Unverified50% confidenceFactExact time
MCP clients serialize the complete tool list into the prompt on every model request, so the token cost equals the length of that JSON text.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMany MCP implementations preload all tool descriptions and JSON Schemas before actually starting work, causing the context window to be filled with metadata.78% similarUnverified每个MCP工具的定义描述、参数schema、使用示例等加在一起可能消耗数百乃至数千token76% similarUnverifiedThe MCP session demonstrated in the article is, at bottom, just 9 JSON messages going back and forth over a pipe, including tool list requests and responses, invocation requests and responses, and some flow control.76% similarVerifiedEach tool in MCP has a strict JSON Schema description, including the name, functional description, and parameter specifications75% similarUnverifiedEarly MCP implementations would inject the complete JSON Schema of all registered tools into the system prompt at once, and connecting to 5 servers could consume approximately 50,000 tokens before the Agent even began working74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1070893API
curl https://kongchang.com/api/v1/knowledge/claims/1070893MCP
get_claim(id=1070893)