Unverified50% confidenceFactExact time
MCP's tools/call is a typical synchronous request-response pattern; even with progress notifications introduced, the caller still expects to get results within a single session.
1
Sources
50%
Confidence
Long-term
Relevance
10/22/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedREST APIs are typically stateless single request-response interactions, whereas MCP supports persistent sessions, making it easy for AI to continuously use the same set of tools across multi-turn conversations.79% similarUnverifiedMCP tool definitions are billed in every round of conversation, regardless of whether a tool is actually called in that round.79% similarUnverifiedMCP uses a request-response model: after the client sends tools/call it waits for the server to return, with no progress pushed in between, and the protocol itself has no background execution semantics.78% similarUnverifiedMCP协议将Function Calling从单次调用扩展为多轮交互的工具使用会话77% similarVerifiedMCP supports progress notification and log feedback mechanisms, allowing an MCP Server to proactively return execution progress and real-time logs to the client during tool execution.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1083854API
curl https://kongchang.com/api/v1/knowledge/claims/1083854MCP
get_claim(id=1083854)