Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

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: up to 2,000 characters as one MP3 in English (40 voices) or Spanish (10 voices) with Deepgram Aura-2, or up to 1,200 characters as one WAV in French, Chinese, Japanese or Korean with MeloTTS. 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 (Aura-2 MP3, many voices), fr, zh, ja or ko (MeloTTS WAV, one voice each); default en
textYesText to speak, up to 2,000 characters (1,200 in fr, zh, ja and ko)
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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false; the description adds genuinely non-derivable context: the price ($0.08/call via x402 USDC or a card key), that failed calls are free, and that because each call is charged 'repeats are not free' — which gives operational meaning to the non-idempotent hint. It also restates that the tool 'reads or computes only and changes nothing'. It stops short of describing latency or response metadata, so not a full 5.

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?

Capability and limits are front-loaded in the first clause, then pricing and routing follow in a logical order; almost every clause carries a fact an agent cannot infer. It is dense but slightly overpacked — the title duplicates the first clause, and price/payment-method detail could be tightened without losing 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?

For a 3-parameter generation tool with no output schema, the description covers output format (one MP3 or one WAV), language-dependent limits, voice selection and defaults, cost and payment paths, failure pricing, and the short-text alternative. Nothing an agent needs to call this correctly or decide against it 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%: the enum for lang, the per-language character caps, the full voice lists and the defaults (luna / aquila) are all already in the schema. The description only restates the character limits and voice counts (40 English, 10 Spanish) and notes voice may be omitted for the default, adding little beyond what structured fields provide. Baseline 3 is appropriate.

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?

The description states a specific verb and resource ('Text to speech for a paragraph or a page') plus hard scope: 2,000 chars / one MP3 for en+es via Deepgram Aura-2, 1,200 chars / one WAV for fr, zh, ja, ko via MeloTTS. It distinguishes itself from a named sibling ('for a sentence of up to 300 characters ai_speech costs less'), so an agent can route 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?

Explicit use cases are enumerated (narration, article and summary read-outs, voice replies, IVR prompts, accessibility), and the alternative is named with the exact condition that selects it (<=300 character sentence -> ai_speech). That is both a when-to-use and a when-not-to-use rule.

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.