Anthropic added the ability to define tools in the system message midway through a conversation to Claude API
Anthropic has made it possible in the beta version of Claude API (header inline-tools-2026-09-15) to define and modify tools directly in the system message midway through a conversation, without having to edit the tools array or invalidate the prompt cache.
Anthropic has made a feature available in the beta version of Claude API that allows tools to be defined directly within the system message midway through an ongoing conversation. The feature runs under the beta header inline-tools-2026-09-15. The tool_addition block can carry a complete tool definition (tool: {"type": "tool_definition", "definition": {...}}), allowing a tool to be added, its schema to be changed, or a switch to a newer version of a server-side tool without having to modify the tools array or invalidate the prompt cache. The same header also covers adding and removing tools by reference.
In combination with the beta header mcp-client-2026-09-15 for the MCP connector, the definition can also be an entire MCP toolset. In this case, the API response records the list of tools loaded from each server in an mcp_tool_listing block, which fixes that list when it is sent back in the next request.
Why it matters
Developers building agents on Claude API can change tools and their schemas throughout a conversation without having to rewrite the entire tools array or lose the benefits of the prompt cache — this reduces both latency and costs for applications with long contexts and intensive tool use, including MCP servers.
Two audiences, two different impacts
What this means
For individuals
Developers working with Claude API and MCP tools can now change tool definitions and schemas during a conversation without having to rewrite the entire call and without losing the prompt cache.
For a business
Companies running agents on Claude API can reduce the costs and latency associated with prompt cache invalidation when updating tools, particularly in production deployments with long contexts or connections to MCP servers.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.