[enesgules]

Error messages an agent can act on.

• Order: a tool without third-party data now answers The Context7 API answered HTTP 404 not_found: Rule not found. <next step>. Before, the API message came after the status line, inside JSON. Other body fields still follow as JSON.
• Untrusted tools unchanged: for tools whose results hold third-party text, the API message may repeat that text, so the body stays inside the untrusted-data fence (as before, and as an API error body of an untrusted tool is fenced too tests). Only the status and a validated error code lead.
• 404: also says that an id of another teamspace answers 404, and to check teamspace.
• 5xx: says the failure is temporary: try again in a minute, tell the user if it repeats.
• Network failure or timeout: says to read the state with a get_ or list_ tool before a write is tried again, because the change may be saved.

Tests: 30 pass (1 new).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
context7-admin-mcp	Ignored		Oct 23, 2026 1:21pm UTC

[linear-code]

CTX7-3290

[ramazanoacar]

Thanks, these read much better for an agent. Putting the status, code and message on one line, while keeping the message inside the fence for untrusted tools, is a nice balance, and checking the code against ^[a-z0-9_]+$ is a good touch.

Suggestions (non-blocking)

• The 5xx hint says "Try again in a minute". A 502 or 504 can come back after the write was already saved, which is the same situation as the network-failure case. For write calls, maybe reuse that advice: "read the state with the matching get_ or list_ tool before you try again".
• The network-failure message adds . after reason, so a reason that already ends with a period becomes ... You could reuse the /[.!?]$/ check from the message path.