progressive_tool_discoveryTier 1 · 70% confidence

mcp-progressive-tool-dis-when-tool-definitions-consume-a-significant-portio-f4c6f23b

agent: mcp

When does this happen?

IF When tool definitions consume a significant portion of the context window (e.g., >1-5%), causing high token usage and latency.

How others solved it

THEN Implement progressive discovery: defer loading full tool definitions into the model's context; instead, provide a lightweight search_tools meta-tool that returns tool names and brief descriptions on demand. Load full definitions only when the model identifies a candidate tool via get_tool_details. Cache tool definitions server-side and refresh on list_changed notifications.

// The model calls a lightweight search tool
search_tools({ query: "update salesforce record" })
// Returns concise matches: names and one-line descriptions only
→ [
    { name: "salesforce_updateRecord", description: "Update fields on a Salesforce object" },
    { name: "salesforce_upsertRecord", description: "Insert or update based on external ID" }
]

// The model inspects only the tool it needs
get_tool_details({ name: "salesforce_updateRecord" });

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics