Skip to main content
Glama

Agent Data Tools: Speech to text and text to speech

Text to speech: long text, up to 2,000 characters as one MP3, natural voices

text_to_speech
Read-only

Text to speech for a paragraph or a page: turn up to 2,000 characters of text into natural, human-sounding speech as one MP3 (base64), in English (40 voices) or Spanish (10 voices), with Deepgram Aura-2. Pick a voice by name or leave the default. Use for narration, article and summary read-outs, voice replies, IVR prompts and accessibility; for a sentence of up to 300 characters ai_speech costs less. Price $0.08/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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
langNoLanguage: en or es (default en)
textYesText to speak, up to 2,000 characters
voiceNoVoice name. English: amalthea, andromeda, apollo, arcas, aries, asteria, athena, atlas, aurora, callista, cora, cordelia, delia, draco, electra, harmonia, helena, hera, hermes, hyperion, iris, janus, juno, jupiter, luna, mars, minerva, neptune, odysseus, ophelia, orion, orpheus, pandora, phoebe, pluto, saturn, thalia, theia, vesta, zeus. Spanish: sirio, nestor, carina, celeste, alvaro, diana, aquila, selena, estrella, javier. Default: luna (en), aquila (es)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint false and idempotentHint false, so the safety profile is known. The description still adds real value beyond them: price ($0.08/call via x402 USDC or card key), failed calls free, repeats charged, and the return payload shape (one base64 MP3). That is more than boilerplate, but pricing/auth is stated as a rate-card fact rather than operational detail (e.g., what happens on quota exhaustion or invalid voice names), so it does not reach the top of the scale.

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?

Front-loaded with capability and limits, then usage, then pricing — a sensible order with no filler sentences. It is dense and somewhat run-on (capability, use cases, price and billing all packed into one paragraph), which slightly hurts scanability, but every clause carries information.

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?

With no output schema, the description correctly supplies the return format (single base64 MP3), plus input limit, language coverage, voice selection behavior, and cost/billing model. Nothing essential for a correct first call is missing.

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% and the schema already enumerates every voice, the lang enum, and per-language defaults. The description only restates the soft guidance 'pick a voice by name or leave the default' and the 40/10 voice counts, adding little meaning the schema does not already carry; baseline 3 applies.

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 and resource — convert text to speech — plus concrete scope: up to 2,000 characters, single MP3, base64, English/Spanish, Deepgram Aura-2. It also distinguishes itself from the sibling ai_speech by input length and cost, so an agent can pick between them without opening either 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 explicit use cases (narration, article/summary read-outs, voice replies, IVR prompts, accessibility) and an explicit when-not with the named alternative: 'for a sentence of up to 300 characters ai_speech costs less.' The selection rule is unambiguous.

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.