MCP/Tool Search
Properties
- tags
- MCP, AI/Coding, Claude Code, OpenAI
MCP Tool Search
- Both Anthropic (Claude/Code) and OpenAI have independently shipped a mechanism for loading MCP tool definitions on-demand rather than injecting all of them into the context window upfront — directly addressing the context bloat problem described in MCP/Concept/On-Demand Tool Loading.
The Problem
Anthropic's Solution: MCP Tool Search (Claude Code)
OpenAI's Solution: Tool Search (GPT-5.4+)
- Tool Search - OpenAI API Docs
- Introduced with
gpt-5.4; tools marked "defer_loading": true are not injected upfront - Two modes:
- Hosted: OpenAI's servers handle discovery automatically; model receives a
tool_search_call then tool_search_output - Client-executed: The application controls discovery logic and returns matching tools via
tool_search_output
- Loaded tools are injected at the end of the context window, preserving cache across requests
- Works with functions, namespaces, or MCP servers
Significance
- Both implementations converge on the same architecture: tools as a searchable index rather than a flat pre-loaded list
- This makes large MCP inventories (dozens of servers, hundreds of tools) practical without the context tax
- Likely to become a baseline expectation for AI coding tools and agent frameworks going forward