Skip to main content
Glama

list_voices

Read-only

Free. Voices for voice_cover: built-in voices (filter by category or search) and the user's own trained voices.

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_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With only readOnlyHint=true in the annotations, "Free" adds real value by disclosing that this call consumes no credits, which is important next to siblings like estimate_credits. However, nothing is said about what a voice entry contains (ids, names, preview URLs) or whether user-trained voices appear when filters are applied.

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?

One compact sentence with the cost fact front-loaded and the resource named immediately. Nothing is padded, though the parenthetical could be tightened into a clearer statement of how the two parameters behave.

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

Completeness3/5

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

For a simple two-parameter, zero-required read tool this is close to adequate, but with no output schema the description should at least sketch the shape of a voice entry so the agent knows what to pass into voice_cover. That gap and the ambiguity over which voices each filter covers keep it at the minimum-viable level.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden. It mentions filtering "by category or search", which maps loosely to the two parameters, but never says what search matches on (voice name, author?) or whether category filtering also narrows the user's trained voices. Meaning added is minimal.

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?

"Voices for voice_cover" names a concrete resource and the sibling that consumes it, and splits the result set into built-in vs. user-trained voices. It is not a bare restatement of the name, though the listing verb itself is only implied.

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

Usage Guidelines3/5

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

The phrase "for voice_cover" implicitly tells the agent to call this before a voice cover to obtain a voice id, and "Free" signals no credit cost. There is no explicit when-not guidance or mention of an alternative source of voices, so usage must be inferred.

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.