Skip to main content
Glama

Text to speech

text_to_speech

Generate speech (priced per 1,000 characters). voice from list_voices.

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": {
      "text": "<text>"
    },
    "name": "text_to_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
modelNo
voiceNo
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, closed-world write, so the safety profile is covered. The description adds genuinely new behavior: billing is priced per 1,000 characters, which tells the agent the call has real cost and that input length matters. It stops short of explaining the `confirm_credits` gate or what the pricing means operationally.

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?

Two short sentences with no filler, and the core action is front-loaded before the pricing and voice notes. It is efficient, though the extreme terseness is part of why key parameters go unexplained.

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?

An output schema exists, so return values need no explanation, but the call-side story is incomplete: a cost-bearing write with a `confirm_credits` parameter and unrestricted `model`/`voice` fields deserves at least a sentence on credit behavior and model selection. As written, an agent could invoke it without understanding the billing guard.

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% across four parameters, so the description must carry the load. It explains where `voice` IDs come from, but says nothing about `model` options, `text` limits, or — most importantly — `confirm_credits`, which appears to be a cost-acknowledgment guard the agent could easily get wrong. One of four parameters clarified is thin compensation.

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 ("Generate speech") — an agent can identify the operation immediately. The parenthetical pricing note and the pointer to `list_voices` for the `voice` argument further pin down what this tool is. It does not, however, distinguish itself from the generic `generate` sibling, leaving ambiguity about which generation entry point to use.

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?

The only routing hint is "`voice` from `list_voices`," which is a parameter-sourcing dependency rather than when-to-use guidance. Nothing says when to choose this over `generate`, whether a text quota or credit balance must exist first, or what happens when credits are insufficient. The agent must infer all usage conditions.

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.

Resources