Need Dynamic Tool Discovery with Client Compatibility
MCP servers exposing dynamic tool discovery still run ahead of client support, leaving a cross-ecosystem compatibility gap that blocks scaling tool catalogs past a handful of agents.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Maya is shipping MCP servers with thousands of candidate tools and a small set of foundational discovery tools — discover-actor, find-actor, fetch-dataset — so an agent can probe and converge on the right tool before invocation. The pattern works; the problem is that many clients still do not support dynamic discovery properly. The capability is ahead of the ecosystem, and the compatibility gap is the bottleneck.
Problem Context
- Platforms with tens of thousands of actors / tools cannot expose them all as prebuilt MCP tools — discovery has to be dynamic
- Apify-class platforms ship foundational discovery tools (discover-actor, find-actor, fetch-dataset) and let agents probe before testing
- Client support for dynamic tool discovery is still uneven; some clients work cleanly, many do not
- This is a cross-ecosystem capability-discovery gap that no single MCP server can close
Problem Impact
- Agents fall back to prebuilt-tool catalogs that cannot represent large tool inventories
- Platforms ship dynamic discovery and then have to maintain “static” parallel exposure for clients that lag
- Developers building on top of these platforms can’t tell which clients will work with the full discovery surface
- The promise of one MCP token for thirty thousand tools stays partial until clients catch up
Naftiko Today
- Executable YAML capability specs can declare both prebuilt and discovery-style exposures, so the same capability can serve clients on either side of the compatibility gap
- MCP exposure layer (Streamable HTTP, stdio) lets a capability publish foundational discovery tools alongside concrete tools
- outputParameters with JSONPath let discovery responses be shaped consistently so clients see predictable structures regardless of upstream tool count
- Spectral ruleset (15 rules) enforces that capabilities advertising discovery follow consistent patterns clients can rely on
Naftiko Tomorrow
- Tool annotations (Second Alpha) will let capabilities mark discovery tools explicitly so clients can opt in to the dynamic surface intentionally
- MCP auth support (Second Alpha) will let clients negotiate discovery scopes with capabilities, narrowing the surface to what the client can actually consume
- Fabric capability discovery (v1.1) will publish capability discovery patterns at the fabric level so the discovery shape is consistent across vendors
- JSON Schema Store publication (GA) will standardize the discovery-tool contract so client implementations converge faster