Unverified50% confidenceFactExact time
Each MCP Server often injects a tool schema at session startup; the more Servers attached to a session, the more tools the model has to weigh at each decision, which both increases token consumption and easily causes confusion in tool selection.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMCP tool definitions are billed in every round of conversation, regardless of whether a tool is actually called in that round.77% similarUnverifiedMCP's working mechanism requires injecting a large amount of context information into model inputs, resulting in excessive token consumption.77% similarVerifiedThe scalability problem with MCP is that the name, description, and schema of each tool must be placed in the system prompt, and 20 servers with 15 tools each would occupy most of the context window.77% similarVerifiedMCP's design philosophy is full registration — tool descriptions from all servers are injected into the context all at once during session initialization.77% similarUnverifiedMCP Host在向大模型发送用户问题时，会同时附带已注册的所有Tool列表，由大模型决定是否调用工具76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1047168API
curl https://kongchang.com/api/v1/knowledge/claims/1047168MCP
get_claim(id=1047168)