Gemini CLI 0.62 MCP titles: reading Sume's tool names

With structured titles, the tool name in a Gemini CLI approval prompt is the exact id the server exposes, so know Sume's: underscore names such as generate_image and generate_video. The Gemini CLI releases page lists v0.62.0 (Sep 29, 2026) with "format MCP tool call titles as structured signatures and segregate explanations".

What to expect in a title

The release note describes the change only in that one line. Treat the title as a signature line, with any explanation shown separately, and confirm the details in your own CLI before relying on a layout.

Sume's naming rules

Live tool ids are underscore names. The server canonicalizes . to _ on call, so a dotted alias such as tools.list still works. Two old names are retired.

Approval checks for paid calls

Mutating and paid tools are hidden until the session has mcp:write or an API key, and paid calls require an idempotency_key. Before approving in the CLI, look for these arguments.

• dry_run=true returns an admission and cost preview without submitting.
• max_spend_usd is enforced only when you provide it.
• idempotency_key is a dedup key, not human approval.
• There is no mcp:paid scope; spend is gated by the wallet and admission.

A safe first call

Ask the server for the contract with tools_schema and then send the paid tool with dry_run=true. Repeat without it only after reading the preview. Use tools_list any time a title shows a name you do not recognize.