Unverified50% confidenceSolutionExact time
In the MCP Python SDK, when a tool error is thrown, the error message is passed back to the model for self-correction; other exceptions are hidden by the SDK as a generic error to prevent stack information from leaking into the prompt.
1
Sources
50%
Confidence
Long-term
Relevance
10/24/2026
First Seen
Sources
MCP Protocol Explained: How a Single Email Can Hijack Your AI Agent
youtubeHaikotek10/24/2026
Related Entities
Related Claims
UnverifiedWhen an MCP tool fails, returning a structured error (such as one containing error and detail fields) is more effective than throwing an exception that becomes a generic error message, and more capable models will self-recover based on detail.71% similarUnverifiedThe fallback error mechanism refers to the SDK using a preset fallback error object instead of failing silently when the primary error information cannot be parsed from the response body.68% similarUnverifiedMisreporting tool execution errors as protocol errors causes the model to miss useful hint information and be unable to self-correct, causing the agent to stop or enter an infinite loop.66% similarUnverifiedBuilt-in SDK error reporting can help API providers distinguish between server-side failures and client-side integration issues, shortening the problem-identification chain.66% similarUnverifiedSending a template variable before it is resolved is a classic incident in API calls: the server may log the request body as-is or echo it back in an error response, exposing the placeholder together with the field name it was meant to protect.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1092996API
curl https://kongchang.com/api/v1/knowledge/claims/1092996MCP
get_claim(id=1092996)