Skip to main content
Glama

Create bilingual interleaved audio

create_bilingual_audio

Turn parallel sentences (language A + language B) into one alternating practice track. Each sentence is spoken by the same neural voices used on bilingualmix.com, then stitched A1→B1→A2→B2 with configurable gaps. Returns a 6-hour download URL (WAV) plus a per-sentence timeline in seconds. Use dry_run=true first to preview the pair list and the cost without spending quota. Free tier: 2 runs / 20 min per day (anonymous, per IP), up to 8 pairs. Signing in doubles it; members get 500 min/month.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_bilingual_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoAlternative to pairs: one sentence per line for language A.
pairsNoSentence pairs. a = first language, b = second language. Leave one side empty to auto-translate (members only).
gap_msNoSilence between a and b of the same pair, milliseconds.
lang_aNoISO language of side a.zh
lang_bNoISO language of side b.en
text_bNoOptional second column, one sentence per line, same line count as text.
dry_runNoPreview pairs and estimated cost only. Free, no quota used.
pair_gap_msNoSilence between consecutive pairs, milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description is consistent with them. It adds genuinely useful context the annotations cannot carry: quota consumption, anonymous-per-IP limits, member-only auto-translate, and the returned artifact shape. It stops short of saying whether generation is synchronous, how long a 6-hour render takes, or what happens on partial failure.

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?

Four sentences, front-loaded with the core transformation before the return value, then quota terms. Dense and mostly waste-free, though the tier/quota sentence is the longest and least essential to invoking the tool correctly.

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 compensates by describing the return value (6-hour WAV download URL plus per-sentence timeline in seconds). For a quota-consuming generation job, the main remaining gap is execution behavior — async vs blocking, duration, and error handling.

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%, so every one of the eight parameters is already documented, including the two enums and the default gap values. The description only echoes the concepts (pairs, configurable gaps, dry_run) without adding syntax or constraints beyond the schema; 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 concrete verb and resource: turn parallel sentences into an alternating practice track, stitched A1→B1→A2→B2, returning a WAV URL plus a per-sentence timeline. The function is clearly distinguishable from align_audio and translate_lines by its output artifact, though no sibling is 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 Guidelines4/5

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

Gives actionable operating guidance: run with dry_run=true first to preview pairs and cost without spending quota, plus the free-tier allowance and member uplift. It does not say when to prefer this over translate_lines (for producing the pairs) or align_audio, so the routing guidance is incomplete.

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.

Resources