Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.301 ·

mcp_call describes a way to keep tool results out of Claude's processing

The description of the mcp_call request now says results skip the usual model-side processing when result_not_for_model is set

You'll notice No documentation found Improvements
JSON All of v2.1.301
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.301,
ImprovementsSection of the release

Unclear Only the request's description mentions result_not_for_model; whether requests already accept it is not confirmed.

What

mcp_call is a request a program controlling Claude Code can send to call a tool on an MCP server (an add-on that provides tools) directly. Its description used to say the result always goes through the same processing as when Claude itself calls the tool. It now says this happens unless result_not_for_model is set.

Why

A program making these calls has an option to get a result that is not prepared for Claude to read.

Read from
Names in the bundlemcp_callresult_not_for_model
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtOnly the request's description mentions result_not_for_model; whether requests already accept it is not confirmed.

See this entry in the whole of v2.1.301 →

Feedback