Developers running agents with dozens of MCP tools get the most out of Google's Tool Retrieval preview, announced November 19.
Developers running agents with dozens of MCP tools get the most out of Google's Tool Retrieval preview, announced November 19. I think this could quietly lower the cost of every agent turn, but I'll believe the savings once someone measures them on a real workload.
- Developers add a tool_search tool and flag functions or remote MCP server tools with defer_loading: true. The model sees names and descriptions upfront and pulls full parameter schemas inside the same API call only when it needs them.
- Google says deferred schemas stay out of the prompt's opening prefix, so the cached prefix stays the same from turn to turn. For tool-heavy agents that cache behavior probably matters more than the headline feature.
- Google charges no separate fee, but it still costs something. tool_search adds a small fixed input block, and loaded schemas are billed at standard rates for the rest of the conversation. Client-side retrieval adds one round trip per search.
- It's in preview for Gemini 3.6 and later, including all Gemini 4 models. Google's 50+ function setup is an example and comes with no benchmark.
I see this as a smart fix for something every MCP builder runs into. Next I'm watching for developer tests on token savings and tool-call accuracy, and for a general availability date. $GOOGL closed at $272.66, down 3.46%, then traded at $274.79 after hours. I wouldn't tie that move to a developer feature.
Source: https://blog.google/innovation-and-ai/technology/developers-tools/gemini-api-tool-retrieval/
Not financial advice. For informational and educational purposes only.
