Skip to main content
Glama

ninerouter_text_to_speech

Convert text into spoken audio using a configured 9Router voice and model. Generate speech from input text for voice-enabled applications and audio playback.

Instructions

Convert text to speech using a configured 9Router voice.

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": {
      "model": "<model>",
      "input": "<input>"
    },
    "name": "ninerouter_text_to_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
modelYes
voiceNo
optionsNoAdditional fields supported by the selected 9Router endpoint.
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds no context beyond that: nothing about cost, latency, whether repeated calls with the same input are deterministic, or what the response actually contains (audio bytes, URL, base64).

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 short, front-loaded sentence with no filler. It is concise in the literal sense, though the brevity reflects under-specification rather than efficiency.

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

Completeness2/5

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

Five parameters, a free-form nested options object, no output schema, and open-world semantics, yet the description covers none of it. An agent cannot tell what the call returns or how voice selection interacts with model selection.

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 only 20% (just the nested 'options' object). The description does not explain the required 'model' or 'input' fields, nor 'voice', 'response_format', or the fact that options pass through arbitrary endpoint-specific fields. It compensates for none of the coverage gap.

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?

States a specific verb and resource ('Convert text to speech') and names the provider voice ('configured 9Router voice'). It is distinguishable from siblings like ninerouter_transcribe_audio or ninerouter_list_voices, though it does not explicitly contrast with them.

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?

No when-to-use guidance, no prerequisites (e.g., that a voice must be configured or chosen via ninerouter_list_voices), and no mention of when a different tool is preferable. The agent must infer everything from the name.

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