Gemini Tool Retrieval preview explained: schema discovery ≠ authorization — how to verify the boundary
TheCodingTutor · reddit · 2026-11-20
Google launched Gemini Tool Retrieval in preview on Nov 19. The author (runs Codorc; AI-assisted, source-checked, not benchmarked) breaks down what agent builders need to know:
- Server-side retrieval keeps tool names/descriptions and loads parameter schemas on demand; retrieving a schema doesn't finish the task.
- Custom functions run in your app; remote MCP uses a separate execution path — verify which you configured.
- previousinteractionid carries history, but tools config must still be supplied on later interactions.
Proposed evaluation: build a fake registry with two similarly named ops, grant the test user access to only one, revoke access after discovery but before execution, and check whether the execution boundary rejects the now-denied action. Keep five trace records per attempt (registry & permissions, retrieved schema, proposed args, authorization decision, outcome), and include a no-match task to see if the agent reports missing capability accurately.
More from coding & agent
- Grok CLI deduplicates a Lumberyard Bistro model, cutting 886,478 triangles (31.3%) — ssh4net · 2026-11-20
- Agent silently failed for 9 days — a dev's fix: every agent sends an 'I ran' heartbeat — Yannxious · 2026-11-20
- Bench-testing Hunyuan Hy4-Flash Q4_K_M to Build a Full Five-Screen Productivity App — TencentHunyuan · 2026-11-20
- Ant Group's Repo-Premium benchmark: BM25 with LLM-written identifiers matches dense code search — hq-bench · 2026-11-20
- An AI industry dev reviews 7 personal agents, from OpenClaw to Claude Duet — none is enough — UpsetScene2929 · 2026-11-20
- Omnigent 0.23.0 ships session grids, /rewind for Claude chats, and cheaper automation polling — matei_zaharia · 2026-11-20