Skip to main content
Glama

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

Dialogue to audio: a script with several speakers as one MP3, plus captions

dialogue
Read-only

Turn a script into a multi-voice conversation: write one line per turn as "Name: text", each speaker gets their own natural voice (Deepgram Aura-2, English or Spanish, or pick voices), and the whole dialogue comes back as one MP3 with SRT captions naming the speaker, timed from the real audio. Up to 6 speakers and 2,500 characters. Use for podcast intros, language-lesson dialogues, explainer videos, ads and game or story scenes. Example: script=Anna: Welcome back to the show! Ben: Thanks, it is great to be here.. Price $0.10/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": {
      "script": "<script>"
    },
    "name": "dialogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage: en or es (default en)
scriptYesOne turn per line as Name: text (up to 6 speakers, 2,500 characters)
voicesNoVoice per speaker, as JSON {"Anna":"luna"} or Anna=luna, Ben=orion (default: a different voice each, in order)
captionsNosrt (default) or vtt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Adds real value beyond annotations: per-call price ($0.10 via x402 USDC or card key), failed calls are free, and repeat calls are not free, which corroborates idempotentHint=false. It also discloses hard limits (6 speakers, 2,500 chars) and that captions are timed from real audio. The statement 'reads or computes only and changes nothing' is consistent with readOnlyHint=true and destructiveHint=false.

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 the core transformation, then constraints, use cases, an example, and pricing. Most sentences carry weight, though the embedded example and pricing tail make it longer than strictly necessary for a 4-parameter tool.

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?

No output schema exists, and the description covers the return: one MP3 with SRT (or VTT) captions naming the speaker. Input constraints, default voice assignment, and cost model are all present, leaving little an agent needs but would not find.

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 the schema already documents lang, script, voices and captions including defaults and the JSON/kv voice syntax. The description reinforces the 'Name: text' line format and supplies a concrete two-speaker example, but adds little beyond what the schema states.

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 concrete verb and resource: turning a multi-speaker script into a single MP3 plus captions, with each speaker voiced separately. That multi-voice framing implicitly separates it from the single-voice TTS siblings, though no sibling is named outright.

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 intended scenarios (podcast intros, language-lesson dialogues, explainer videos, ads, story scenes), which is helpful context for selection. It never states when NOT to use it or points to the single-voice alternatives like text_to_speech or text_to_speech_captions, so the agent must infer the boundary.

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.