Skip to main content
Glama

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

Dubbing, dub audio: translated voice track in 6 languages, plus subtitles

dub
Read-only

Dub a clip: speech in any of 90+ languages is transcribed, translated and spoken again, with translated SRT on the original timings. New voice in English or Spanish (Aura-2 MP3, pick a voice, up to 2,500 characters) or French, Chinese, Japanese or Korean (MeloTTS WAV, up to 1,200 characters). MP3/WAV up to 10 minutes or other formats up to 2 MB, by URL or upload. Keeps the order, not exact timing. Use for course clips and product videos. Example: url=https://upload.wikimedia.org/wikipedia/commons/7/77/Tofino_pronunciation.mp3, to=es. 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": {
      "url": "<url>",
      "to": "<to>"
    },
    "name": "dub"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLanguage of the new voice: en, es, fr, zh, ja or ko
urlYesAbsolute http(s) URL of the recording (MP3/WAV up to 10 minutes; M4A, OGG or WebM up to 2 MB); or POST the file itself (raw body, multipart `file` part, or base64 in JSON)
fromNoSpoken language of the recording (default: detected)
voiceNoAura-2 voice for an en or es track (default luna for en, aquila for es); fr, zh, ja and ko have one voice each

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false and destructiveHint=false, yet the description adds substantive extras: per-language output format (Aura-2 MP3 vs MeloTTS WAV), character ceilings of 2,500 vs 1,200, 'keeps the order, not exact timing', and full pricing ($0.10/call via x402 USDC or card key, failed calls free). The clauses 'Reads or computes only and changes nothing' and 'each call is charged, so repeats are not free' largely restate the annotations, which keeps this from a 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?

Content is front-loaded: the operation and outputs come first, then format/language constraints, then usage and pricing. It is dense but every sentence carries constraints an agent needs. Minor waste in the redundant reassurance that it 'changes nothing' and the restated idempotency note.

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?

There is no output schema, and the description compensates by naming both deliverables — the dubbed voice track (with format per language) and the translated SRT on original timings. Combined with input size limits, character caps, cost model and failure pricing, an agent has everything needed to call this correctly and predict the bill.

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 baseline is 3 and all four parameters are already documented in the schema. The description does add real semantics beyond it — that a picked voice applies only to en/es while fr/zh/ja/ko have a single fixed voice, and the differing character limits per language path — but it omits the 'from' auto-detect behavior and voice defaults, which the schema carries alone.

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?

The description opens with a precise verb and resource: 'Dub a clip: speech in any of 90+ languages is transcribed, translated and spoken again, with translated SRT on the original timings.' That makes the input-process-output chain unmistakable. It never names or contrasts with siblings like audio_transcribe or subtitles_translate, so an agent must infer the boundary rather than being told it.

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

Usage Guidelines4/5

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

'Use for course clips and product videos' plus a concrete example (url=…wikimedia…mp3, to=es) gives clear positive context for selection. There is no when-not guidance and no pointer to the obviously adjacent siblings (plain transcription, subtitle-only translation), so exclusion logic 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.