Skip to main content
Glama

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

Text to speech with subtitles: one MP3 plus SRT or VTT timed to the voice

text_to_speech_captions
Read-only

Text to speech that comes with subtitles: up to 2,000 characters spoken as one MP3 in English or Spanish (Deepgram Aura-2, pick a voice), plus SRT or VTT captions whose timings come from the generated audio itself, sentence by sentence. Ready for a video editor, no transcription step. Use for narrated videos, social clips, e-learning and accessible audio with captions. 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_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage: en or es (default en)
textYesText to speak, up to 2,000 characters
voiceNoAura-2 voice name (default luna for en, aquila for es)
captionsNosrt (default) or vtt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing price ($0.08/call), payment paths (x402 USDC or card key via /credits), and that failed calls are free while repeats are charged — usefully reinforcing idempotentHint=false. Some phrasing ('changes nothing', 'repeats are not free') merely restates readOnlyHint and idempotentHint rather than adding new behavior detail.

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?

The core capability and hard limits are front-loaded, followed by use cases and then cost/payment terms. It is dense and largely waste-free, though the long run-on clauses make it slightly harder to scan than a bulleted structure would be.

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 single-shot generation tool with no output schema, it covers output artifacts (MP3 plus SRT or VTT), language and length limits, cost, and that no separate transcription step is needed. Only minor gaps remain, such as latency expectations or what a failure response looks like.

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%, so language enum, default voice selection, caption format, and the 2,000-character limit are already documented in the schema. The description only adds that voices come from Deepgram Aura-2, which is a small increment over structured data; baseline 3 applies.

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: text is spoken as a single MP3 while SRT/VTT captions are timed from the generated audio sentence by sentence. The subtitle-included scope implicitly separates it from plain TTS siblings like text_to_speech, though none are named explicitly.

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

Usage Guidelines3/5

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

Lists concrete use cases (narrated videos, social clips, e-learning, accessible audio with captions) which gives implied usage context. However, it never states when NOT to use it or names an alternative such as a plain TTS or translation tool, so selection against siblings is left to inference.

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.