Skip to main content
Glama

Kubeez

play_gemini_omni_voice

Read-onlyIdempotent

Scope: none. Return a single voice's preview audio URL so the user (or the agent) can hear how a Gemini Omni voice sounds before using it in a generation. Faster than list_gemini_omni_voices when you already know the id (e.g. user said 'play me Kore' or you just picked one from the catalog). ARGS: voice_id — one of the 30 known ids (e.g. kore, puck, achernar). Unknown ids return invalid_voice_id with a hint to call list_gemini_omni_voices. RETURNS: { voice: {id, label, gender, description, preview_url}, preview_url, message }. The preview_url is a ~7s mp3 hosted on the Kubeez web app — surface it directly to the user so they can play it. USE WHEN: the user asks 'what does sound like', 'play that voice', or you want to confirm a pick before passing it to generate_media.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "voice_id": "<voice_id>"
    },
    "name": "play_gemini_omni_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint, idempotentHint, non-destructive, closed-world), so the baseline is low; the description still adds real behavior: unknown ids return `invalid_voice_id` with a hint to call the sibling lister, and the payload includes a ~7s mp3 preview_url that should be surfaced to the user. That error-path and side-effect-free framing is exactly the extra context annotations can't carry.

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?

Structured as Scope / ARGS / RETURNS / USE WHEN and front-loaded with the core action, so it is scannable despite its length. The leading 'Scope: none' is cryptic and the RETURN block partially duplicates the output schema, but no sentence is wasted for a tool of this complexity.

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?

For a one-parameter read tool this covers everything an agent needs: purpose, argument domain, error case, return payload, and how to present the result to the user. The output schema makes the RETURN section redundant but not incorrect, and nothing material is missing.

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

Parameters5/5

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

Schema coverage is 0% (`voice_id` is an undescribed string), so the description must compensate and does: it states the value is one of 30 known ids, gives concrete examples (`kore`, `puck`, `achernar`), and defines the failure behavior for unknown ids. An agent knows both the accepted domain and the recovery path without any schema help.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Return a single voice's preview audio URL' for a Gemini Omni voice. It names the two siblings it could be confused with (`list_gemini_omni_voices` for browsing, `generate_media` for actual generation) and states the tradeoff, so an agent can distinguish it without opening any schema.

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 triggers are given ('what does <voice> sound like', 'play that voice', confirming a pick before `generate_media`), plus the key exclusion: prefer `list_gemini_omni_voices` if you don't already have the id. Both when-to-use and when-to-use-something-else are covered.

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