Unverified50% confidenceFactExact time
MCP tools declare their own semantics through annotations (such as readOnlyHint and idempotentHint), and the client decides the retry strategy accordingly; only tools explicitly marked as read-only or idempotent are suitable for automatic retry when a connection is interrupted.
1
Sources
50%
Confidence
Long-term
Relevance
10/21/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedIn MCP, tools are functions that the model can execute, resources are read-only data with no side effects, and prompts are reusable templates that users actively select.79% similarUnverifiedreadOnlyHint and destructiveHint are metadata fields built into the MCP specification for communicating the degree of side effects of a tool to agent frameworks.78% similarUnverifiedThe MCP protocol specification allows a Server to dynamically declare at runtime the subset of capabilities it supports, so the Host does not need to hardcode tool knowledge in advance and can automatically adapt simply by reading the Server's capability list.78% similarVerifiedMCP implements runtime dynamic tool discovery through the tools/list method without requiring hardcoded interfaces, which is a core advantage over traditional REST API integration.77% similarUnverifiedThe MCP tool call success rate is affected by instruction clarity: with short, vague instructions (such as 'list semua pm') the Agent cannot call the tools correctly, while with a complete phrasing (such as 'use IdCloudHost's MCP to check current usage') it succeeds.77% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1083597API
curl https://kongchang.com/api/v1/knowledge/claims/1083597MCP
get_claim(id=1083597)