Skip to main content
Glama

list_voices

Discover installed text-to-speech voices with name, accent, gender, and quality grade before calling speak(); also shows available effects and whether ffmpeg was found.

Instructions

Text to speech voices installed for speak(): name, accent, gender and Kokoro's quality grade (A best, F worst; higher grades had more and cleaner training audio), the effects available, and whether ffmpeg (for effects and OGG output) was found.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden, and it does well: it explains what the quality grade means (A best, F worst, based on training audio volume and cleanliness) and flags that ffmpeg availability gates effects and OGG output. That is real behavioral context an agent needs. It omits an explicit 'read-only, no side effects' statement, so it is not a 5.

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?

A single front-loaded sentence listing the returned fields, with one parenthetical parenthetical explaining the grade scale. The parenthetical earns its place because the grade letters are otherwise meaningless, though it does stretch the sentence.

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?

There is no output schema, so the description must describe the return payload, and it does enumerate the key fields. However, it does not indicate the return shape or format (list vs object, per-voice structure), which leaves a modest gap for a discovery tool whose whole value is its output.

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?

The tool takes zero parameters, which establishes the baseline of 4. The description correctly adds no parameter discussion, so there is nothing misleading or redundant.

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?

The description identifies a specific resource — the text-to-speech voices available to speak() — and enumerates the fields returned (name, accent, gender, quality grade, effects, ffmpeg presence). It also ties itself to the sibling speak(), so an agent can tell this is the discovery step that precedes synthesis. It stops short of a leading verb phrase like 'List the voices', which keeps it from a 5.

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 reference to 'speak()' implies this is the tool you call before/instead of guessing a voice name, and the mention of ffmpeg implies you check this before requesting effects or OGG output. Those conditions are implied rather than stated, and there is no explicit 'use this instead of X' or 'call this first' instruction.

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