Unverified50% confidenceDecision RuleExact time
Developers should by default encapsulate business-logic-level errors (invalid parameters, non-existent resources, insufficient permissions, etc.) as tool errors; only genuine protocol violations should trigger a JSON-RPC error response.
1
Sources
50%
Confidence
Long-term
Relevance
10/5/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedA protocol error means the request itself is malformed (e.g., calling a non-existent tool name) and is returned as a standard JSON-RPC error.75% similarUnverifiedWhen managed configuration files, drop-in configurations, MDM plists, or HKLM registry values cannot be correctly parsed, Claude Code will refuse to start and indicate the source of the problem, adopting a fail-closed security design.62% similarUnverifiedThis update fixes the issue where sessions failed on every turn due to the API error "role 'system' must precede an 'assistant' message".57% similarUnverifiedPrior to mloda 0.11, a resolution failure returned only a single-line error message, unable to indicate whether the name was misspelled, the domain was misconfigured, or a required option was missing.57% similarUnverifiedResumate's failure detection is exception-based and cannot detect "wrong but valid" outputs that contain incorrect content without throwing an exception.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/977139API
curl https://kongchang.com/api/v1/knowledge/claims/977139MCP
get_claim(id=977139)