Skip to main content
Glama

Render a [PAUSE n] script to one MP3

render_script

Converts a markdown script into one continuous MP3, inserting exact silent pauses and synthesizing sentence segments, then returns the file path, duration details, and audio.

Instructions

Renders a markdown script into a single continuous MP3. Lines consisting only of "[PAUSE n]" become n seconds of real silence; text is split at sentence boundaries and synthesised segment by segment, then joined on MP3 frame level without re-encoding. Returns the file path, the measured total duration and the duration of every segment, plus the MP3 as an audio block (up to 8 MB, unless TELNYX_TTS_EMBED_AUDIO=false).

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>",
      "voice": "<voice>"
    },
    "name": "render_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoSpeaking rate multiplier (1 = normal). Mapped per provider: voice_speed for Telnyx Ultra/Grok, speed for Minimax/Soniox, SSML <prosody rate> for AWS Polly and Azure. Other providers reject it.
voiceYesVoice id in Provider.Model.VoiceId format, e.g. "Telnyx.Ultra.Clara" or "aws.Polly.Vicki".
scriptYesMarkdown script. Lines that consist only of "[PAUSE n]" become n seconds of real silence; headings, horizontal rules and note lines mentioning the markers are not spoken.
languageNoBCP-47 language code, e.g. "de-DE". Used by AWS Polly, Azure, ElevenLabs, Inworld and Soniox; ignored by other providers.
file_nameNoBase name for the MP3.
max_charsNoMaximum characters per synthesis request (default 1800).
voice_settingsNo
lead_in_secondsNoSilence before the first segment.
lead_out_secondsNoSilence after the last segment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=true), the description discloses important behavior: synthesis happens per segment without re-encoding, the return payload includes file path, total duration and per-segment durations, and the MP3 is embedded as an audio block capped at 8 MB with a TELNYX_TTS_EMBED_AUDIO override. It stops short of saying where the file is written or whether an existing file with the same file_name is overwritten.

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?

Three dense sentences, front-loaded with the core outcome before mechanics and return values. Nothing is redundant, though the return-value clause is a long run-on that could be tightened.

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?

For a 9-parameter tool with a nested object and no output schema, the description covers what the tool produces (file path, durations, embedded audio), how silence and segmentation work, and the size cap — everything an agent needs to decide to call it and interpret the result.

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 89%, so the schema already documents rate, voice, language, max_chars, lead-in/out and the nested voice_settings. The description reinforces the [PAUSE n] semantics and the segment-joining model that motivates max_chars, but adds little syntax or format detail beyond what the schema provides.

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 specific verb and resource: 'Renders a markdown script into a single continuous MP3', and clarifies the segment-by-segment synthesis plus frame-level joining. It is clearly distinguishable from a single-utterance 'speak' tool, though it never names or contrasts any sibling 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?

Usage is implied by the mechanics described (multi-segment scripts with [PAUSE n] markers, joined into one file), but there is no explicit statement of when to prefer this over 'speak' or when to run 'estimate_cost' first. No exclusions or prerequisites such as provider/voice compatibility requirements are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools