Skip to main content
Glama

list_voices

Lists available speech voices for a specific TTS provider, or all configured providers when omitted, so agents can select a voice for synthesis.

Instructions

List voices for one provider, or all configured providers when omitted.

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
providerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. "List" implies a safe read and "configured providers" hints that the no-argument case aggregates across configuration, but nothing is said about permissions, result size, or ordering. The presence of an output schema relieves it of describing return values.

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

Conciseness5/5

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

One sentence, front-loaded with the action and immediately followed by the scope/branch behavior. No filler and nothing an agent must read past to find the operative rule.

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

Completeness4/5

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

For a one-optional-parameter listing tool with an output schema, the definition covers what the tool does and how the parameter changes scope. Only minor gaps remain, such as what identifiers or fields a voice entry contains, which the output schema presumably handles.

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?

Schema coverage is 0% for the single optional provider parameter, so the description must compensate. It does explain the meaningful behavior: omitting provider means all configured providers, which is the key semantic an agent needs beyond the bare null default in the schema.

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 gives a specific verb and resource ("List voices") plus the scoping condition (per-provider vs. all configured providers). That clearly separates it from siblings like list_providers, provider_status, and synthesize, though it never names them explicitly.

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

Usage Guidelines4/5

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

It states the two operating modes and the condition that selects between them: supply a provider for one, omit it for all configured providers. There are no exclusions or named alternatives, but the usage context is unambiguous for a one-parameter listing tool.

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

Deploy Server

Other Tools