Two synthetic document fixtures through McpWorkbench 0.7.5: native JSON text round-trips, no model required #8224
ashevilleislove
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm sharing this on behalf of Ardaro, which operates the linked service. This example was prepared with AI assistance and checked against the live service. It is a small native
McpWorkbenchsmoke test for people wiring remote MCP tools into AutoGen before adding an agent or model.The useful detail here is the return type: in AutoGen 0.7.5,
call_tool()returns an AutoGenToolResult. The example parses the JSON from itsTextResultContent, rather than assuming it exposes the MCPstructuredContentfield.It calls exactly two free, fixed synthetic fixtures on our server: a receipt example and an invoice/purchase-order comparison example. Neither accepts customer documents. No model, API key or wallet is needed for these two calls.
Tested on Python 3.11 with:
The MCP pin is deliberate: in this clean environment, an unpinned install selected MCP 2.2.0 and AutoGen import failed on
mcp.shared.context.RequestContext, before any server request. The combination above completed the live check.Observed output on 2026-09-13 UTC:
The bounded verification recorded five HTTP requests: initialization, its notification, tool discovery, and the two fixture calls. The server advertised 18 tools; the code explicitly selects only the two names above. Both result identities matched a locally recomputed SHA-256 of the canonical result JSON. That checks content consistency, not document authenticity or accounting approval.
This exercises native Workbench transport, tool-result conversion and the review boundary using fixed examples. It does not validate arbitrary receipt parsing, OCR, paid x402 execution, production data privacy or token savings. Other server tools have separate terms and may require payment; these example calls do not authorize them. Accounting actions still require human review.
AutoGen MCP Workbench documentation Β· Ardaro service details
All reactions