AI News ai-agents mcp
AI News Info

Gemini API adds Tool Retrieval preview for on-demand tool schemas

Tool Retrieval is now in preview in the Gemini Interactions API, letting agents load tool parameter schemas on demand instead of sending the full tool library in every prompt.

KT Kusal Tharindu

Tool Retrieval is now in preview in the Gemini Interactions API (application programming interface). It lets an agent load tool parameter schemas on demand instead of sending the full tool library in every prompt. The model still sees the name and description of every deferred tool, so it knows what is available, but the parameter schemas stay out of context.

Why it matters

The feature is designed to reduce input tokens and keep tool selection accurate as an agent scales. There is no index to build or host because Gemini runs the search on the server. Tool Retrieval also works with remote MCP (Model Context Protocol) servers in the Gemini API.

What to do

To turn on Tool Retrieval, add a tool_search tool to the request and set defer_loading: true on the tools to hold back. Setting defer_loading: true on an mcp_server tool loads every tool that server exposes on demand. Client-side retrieval is enabled by declaring tool_search with execution set to client. That path adds one round trip per search because the app runs the lookup.

Availability and cost

Tool Retrieval works with Gemini 3.6 and later models, including all Gemini 4 models, in the Interactions API. It has no separate charge; input and output tokens are billed at standard rates for the model called.

Sources

  1. Introducing Tool Retrieval in the Gemini API
3 posts

Discussion

Spotted an error? Send corrections to [email protected] .

Search Oxelan Signal

Type to search the archive.

Search by title, tag, summary or body text.