Unverified80% confidenceFactExact time
每次MCP调用都会产生大量Token消耗，且由于需求动态变化，这些消耗无法像固定文档那样被缓存复用
1
Sources
80%
Confidence
Medium-term (~90 days)
Relevance
5/25/2026
First Seen
Valid until: 8/23/2026(expired)
Sources
UE5+AI实战：用MCP打通蓝图与C++开发全流程
bilibili虚幻小刚5/25/2026
Related Entities
Related Claims
UnverifiedMCP的工作机制需要将大量上下文信息注入模型输入，导致Token消耗过大76% similarVerified同时连接多个 MCP 服务器时，仅工具描述就可能消耗数千甚至上万 tokens69% similarUnverified工具层用大模型搭配Function Calling或MCP协议处理复杂需求，只能做兜底，不能承载主流量，否则用户量上涨成本会严重超支67% similarUnverifiedUnder the traditional MCP calling approach, intermediate data (such as a meeting recording transcript) enters the context twice—once when read and once when passed as a parameter—causing redundant token consumption66% similarUnverified每个MCP加载时其工具描述会被塞入上下文，若给Agent附加大量MCP且不限制Tools，会导致token爆炸、延迟增加和成本上升66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1722API
curl https://kongchang.com/api/v1/knowledge/claims/1722MCP
get_claim(id=1722)