Particle.news

Google Adds Tool Retrieval to Gemini Interactions API

The preview change cuts token costs and latency by loading tool parameter schemas only when the model requests them.

Overview

  • Google announced the feature Thursday and made Tool Retrieval available in preview inside the Gemini Interactions API.
  • Developers enable it by adding a tool_search tool and setting defer_loading: true so the model sees tool names and descriptions but only loads full parameter schemas when it requests a tool by name.
  • Tool Retrieval runs server-side by default so each schema is pulled and the resulting function call happens inside the same API request, which keeps interaction logs for debugging.
  • The feature supports Gemini 3.6 and later, including all Gemini 4 models, and has no separate fee because input and output tokens are billed at the model’s standard rates while each loaded schema is counted as input for the rest of the conversation.
  • Google offers a client-side execution option that adds one round trip for apps that maintain their own registry and also supports deferring tools exposed by remote MCP servers, but the preview status means developers should measure token savings and validate retrieval accuracy before using it in production.