← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Gemini API Introduces Tool Retrieval for Efficient Tool Management

🔄 Updated 2d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Tool Retrieval is now in preview for the Gemini API.
  • Defers loading of tool parameter schemas until requested.
  • Reduces input token counts and latency for agents with many tools.
  • Improves tool-selection accuracy by keeping schemas out of context.

New Tool Retrieval Feature

Google has introduced Tool Retrieval in the Gemini API, now available as a preview feature within the Interactions API. This new capability addresses challenges faced by agents that connect to numerous tools, where sending full parameter schemas for every tool on each request can lead to inefficiencies.

Addressing Performance Issues

Previously, agents with dozens or hundreds of tools would send all tool parameter schemas with every request. This practice inflated input token counts, increased latency, and decreased the accuracy of tool selection as the list of candidates grew. Tool Retrieval aims to mitigate these issues by optimizing how tool information is handled.

How Tool Retrieval Works

To activate Tool Retrieval, developers add a 'tool_search' tool to their request and set 'defer_loading: true' on specific tools. The model still receives the name and description of all deferred tools, allowing it to understand available functionalities, but their parameter schemas remain out of context. When a tool is required, the model requests it by name, the API loads the full schema, and the model then executes the function call, all within a single API request.

Simplified Implementation

The implementation requires minimal code changes: adding the new 'tool_search' tool and a flag to defer loading on desired tools. Gemini handles the search process on the server side, eliminating the need for developers to build or host an index. The entire process, from tool search to function call, is logged in the interaction steps, aiding in debugging tool names and descriptions.

Impact on Agent Development

This feature is significant for developers building agents that interact with a large number of external tools. By reducing token usage and latency, it allows for more complex and responsive agent behaviors without incurring prohibitive costs or performance penalties. It also contributes to more precise tool selection by the model, as it only processes relevant schema information when necessary.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Google has launched Tool Retrieval in the Gemini API, available in preview, which allows agents to manage large tool libraries more efficiently. This feature defers loading of tool parameter schemas until needed, reducing input token counts, latency, and improving tool-selection accuracy.