Skip to main content
Glama

Kubeez

list_gemini_omni_voices

Read-onlyIdempotent

Scope: none. Return the 30-voice catalog for Gemini Omni Video. Each entry has an id (forward as voice_id to generate_media), label, gender (female / male / ungendered), and a one-line character description (e.g. 'Soft, high pitch'). USE WHEN: the user wants to pick a voice for a gemini-omni-video-* / gemini-omni-flash-* generation, or you want to suggest 2–3 fitting voices for the prompt before calling generate_media. For a CONSISTENT voice across many clips, bind the chosen id to a saved character (pass it as voice_id in manage_library(kind='character', action='create', ...)) so every generation that reuses the character inherits the same voice. Static list, safe to call without consuming credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_gemini_omni_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the substantive extra detail that it is a static list that consumes no credits, which is genuinely beyond the annotations, but says nothing further about call behavior or latency since the return shape is covered by the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads 'Scope: none', then the catalog contents, then the usage triggers and the consistency tip, so scanning order matches decision order. The character-description example ('Soft, high pitch') and the inline `manage_library` call signature are slightly verbose but each carries real routing value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema already documents the returned fields and annotations cover safety, so the description only needs to explain purpose, when-to-use and downstream wiring, all of which it does. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so no parameter semantics are needed; baseline 4 applies. The description usefully explains how the returned `id` maps to a `voice_id` input on other tools, which is cross-tool semantics rather than parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return the 30-voice catalog for Gemini Omni Video') with scope ('none') and enumerates the returned fields. It doesn't explicitly negate the closest sibling, `play_gemini_omni_voice`, which an agent might otherwise confuse with auditioning a voice, so sibling differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'USE WHEN' clause covers two concrete triggers: the user wants to pick a voice for a gemini-omni-* model, or the agent wants to suggest 2–3 fitting voices before calling `generate_media`. It also adds a downstream workflow (binding the id to a saved character via `manage_library` for consistency across clips), which fully routes the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources