Repository navigation
Client example proposal: host-side bounded retrieval over large tools/list catalogs #3617
Closed as not planned
Description
The current SDK docs make an important boundary explicit: servers should list tools normally and filtering is the host's job. That matches a validation experiment I am running with SchemaRouter, a typed capability/field retrieval layer.
I would like to contribute only a client-side example/benchmark, not a protocol or server change:
- fetch a deliberately large
tools/listcatalog with the normal Python SDK client; - build/update a typed local capability index from those tool schemas;
- for each query retrieve a bounded relevant subset for host/model exposure;
- keep MCP sessions, notifications, tool calls, and server semantics unchanged;
- when
ToolsListChangedarrives, refetch and refresh the index rather than assuming the delta.
The comparison would report required-tool recall, exposed schema/context size, unsupported-query rejection, and refresh behavior after tool-list changes.
Would this be appropriate as a client example/story in this repository, or should host-side tool selection examples live outside the SDK? I would wait for maintainer guidance before opening code.
Activity
maxisbey commentedon Oct 6, 2026
Thanks for asking before writing any code. This one is better kept outside the SDK, so I'm going to close it as not planned.
We'd like the examples in this repo to run on the SDK alone, with no third-party package, and to show how to use the SDK rather than how a host picks tools. As you say, tool selection is the host's job, so a benchmark for it fits better in your own repository.
AI Disclaimer
Generated by Claude Code