| Filename | Latest commit message | Latest commit date |
|---|---|---|
The surrounding sentence names 2026-07-28 as the revision that first allows an array-rooted schema, but the link pointed at /draft, which moves on to the next revision and stops matching the claim. Came in with #164. The same fix is on the open Go, Rust, and Ruby branches. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
| .. | ||
| .env.example | ||
| .python-version | ||
| client.py | ||
| pyproject.toml | ||
| README.md | ||
| uv.lock | ||
An LLM-Powered Chatbot MCP Client written in Python
See the Build an MCP client tutorial for more information.
Structured content
call_tool validates every result against the tool's declared output schema, so the spec's client-side SHOULD needs no code here.
The two channels go to different readers: content is forwarded to the model, while structured_content is used as data — when a tool returns an array, the client counts its items rather than re-reading the prose. See Structured Content.
Client(transport, mode="auto") probes server/discover and falls back to the 2025-11-25 handshake; client.protocol_version reports which era you got. See Protocol versions.