Skip to main content
Glama

ninerouter_list_voices

Read-onlyIdempotent

Retrieve available text-to-speech voices by provider, optionally filtered by language, to select the right voice for speech synthesis.

Instructions

List text-to-speech voices for a provider and optional language.

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": {
      "provider": "<provider>"
    },
    "name": "ninerouter_list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the filtering behavior (provider-scoped, optional language), and says nothing about whether unknown providers error out, whether the list is live from the upstream provider, or what the response contains. That is modest added value given strong annotations.

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 with no filler; the required/optional distinction is packed in compactly. It is terse to the point of omitting format detail, but nothing is wasted.

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-param read tool with no output schema and full annotation coverage, the description is functional but under-specified: the shape of returned voices and acceptable provider/lang values are absent, which matters for an open-world tool that calls an external provider.

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

Parameters3/5

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

Schema description coverage is 0% for two parameters, so the description must carry the format burden. It does name both parameters and their roles (provider required, language optional), but gives no format or examples for either, so an agent still cannot know whether provider expects 'openai' or a URL, or whether lang is 'en' versus 'en-US'.

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 uses a specific verb ('List') plus a precise resource ('text-to-speech voices') and states its scoping dimensions (provider, optional language). It is clearly distinguishable from the sibling ninerouter_text_to_speech, which synthesizes audio rather than enumerating voices, though it names no sibling explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of the natural pairing with ninerouter_text_to_speech (e.g., 'discover valid voice IDs before synthesis'), and no exclusions. The usage is only implied by the verb 'List'.

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