Skip to main content
Glama

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

Text to speech (TTS): natural voices, audio file

ai_speech
Read-only

Turn up to 300 characters of text into natural, human-sounding speech: MP3 in English (40 voices) or Spanish (10 voices) with Deepgram Aura-2, or WAV in French, Chinese, Japanese or Korean with MeloTTS (one voice each). Pick a voice by name or leave the default. Use for voice replies, audio notes, accessibility and phone or chat bots; for up to 2,000 characters use text_to_speech. Example: text=Your payment was received. Thank you!. Price $0.01/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": "ai_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 300 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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, destructiveHint=false and idempotentHint=false; the description adds real value on top by explaining the pricing ($0.01/call via x402 USDC or card key, failed calls free) and the practical consequence that repeats are not free, which is the 'why' behind non-idempotency. It does not disclose latency, output size/duration, or how the audio is returned, so it stops short of full behavioral disclosure.

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 scope, then usage, then pricing — a sensible order with no filler sentences. It is densely packed (language/format/voice counts, price, payment rails in one paragraph) and could be split for scanability, but every sentence carries information.

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

Completeness4/5

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

For a 3-parameter, no-output-schema tool it covers capability, formats per language, defaults, limits, cost, and side-effect profile. The notable remaining gap is response shape — whether audio is returned inline, as base64, or as a URL — which matters because there is no output schema to fall back on.

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 coverage is 100% and the schema already enumerates every language and voice name with defaults, so the description's 'pick a voice by name or leave the default' and language/voice-count summary add emphasis rather than new semantics. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb and resource (text → speech), with concrete scope: 300-character cap, MP3 via Deepgram Aura-2 for en/es, WAV via MeloTTS for fr/zh/ja/ko. It explicitly distinguishes itself from the sibling text_to_speech for the 2,000-character case, 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?

Names concrete use cases (voice replies, audio notes, accessibility, phone/chat bots) and an explicit alternative with its selection condition: 'for up to 2,000 characters use text_to_speech.' The default-voice option and the cost model are also stated up front.

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.