Skip to main content
Glama

Text-to-Speech

tts
Read-only

Convert text to speech audio. Returns the speech as base64 MP3 audio with its sample rate and bit rate (read from the audio itself) and the voice used. Use for spoken voice or narration, up to 2,000 characters a call. For sound effects or music use sound-generate. Cost: 2 credits, charged only when a call succeeds.

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": "tts"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to convert (max 2000 chars).
providerNoTTS provider.auto
voice_modelNoDeepgram voice model ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint, non-destructive, closed-world), so the description carries the rest and does so well: base64 MP3 return format, sample rate and bit rate read from the audio, the voice used, and a per-call character ceiling. The cost disclosure ('2 credits, charged only when a call succeeds') is exactly the kind of operational detail annotations never encode.

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?

Four short sentences, front-loaded with purpose and return shape, then limits, then the sibling exclusion, then cost. Every clause carries distinct information; nothing is repeated from the title or wasted.

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

Completeness5/5

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

There is no output schema, but the description compensates by describing the return payload (base64 MP3, sample rate, bit rate, voice used). Combined with the character limit, billing rule, and sibling routing, an agent has everything needed to call it correctly and predict the result.

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 100%, so all three parameters (text, provider enum, voice_model) are already documented in the schema, which sets the baseline at 3. The description only restates the 2,000-character limit and adds nothing about provider selection or voice_model behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Convert text to speech audio') and immediately makes it distinguishable from the audio-generation sibling by naming sound-generate as the alternative for effects/music. An agent can pick this over its siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('spoken voice or narration, up to 2,000 characters a call') and an explicit when-not with the alternative tool named ('For sound effects or music use sound-generate'). The only inference left is which TTS sibling to avoid among stt/transcribe, which is unambiguous from the verb.

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.