Skip to main content
Glama
Sign In
Advanced TTS MCP Server

Advanced TTS MCP Server

by samihalawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

batch_synthesize

Transform multiple text segments into audio with customizable voice, speed, emotion, and pacing. Optionally merge segments into a single file for efficient TTS processing.

Instructions

Synthesize multiple text segments with optional merging and intelligent pacing

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": {
      "segments": "<segments>"
    },
    "name": "batch_synthesize"
  }
}

Input Schema

NameRequiredDescriptionDefault
emotionNoVoice emotion for all segmentsneutral
filenameNoCustom filename for saved audio
mergeOutputNoMerge segments into single file
outputFormatNoAudio output formatwav
pacingNoSpeech pacing style for all segmentsnatural
saveFileNoSave audio to file
segmentPauseNoPause between segments in seconds
segmentsYesList of text segments to synthesize
speedNoSpeech speed (0.25-3.0)
voiceIdNoVoice to use for all segmentsaf_heart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'optional merging and intelligent pacing,' which adds some context about output behavior, but fails to cover critical aspects: whether synthesis is resource-intensive, if there are rate limits, authentication needs, error handling, or what the output entails (e.g., audio files, metadata). For a tool with 10 parameters and no annotations, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence: 'Synthesize multiple text segments with optional merging and intelligent pacing.' It is front-loaded with the core action and key features, with zero wasted words. Every element earns its place by conveying essential information without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (10 parameters, no output schema, no annotations), the description is incomplete. It lacks details on output behavior (e.g., what is returned, file handling), error conditions, performance implications, and how it differs from siblings like 'synthesize_speech.' For a batch synthesis tool with rich parameters, the description should provide more context to guide effective use.

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%, meaning all parameters are documented in the input schema. The description adds minimal value beyond the schema—it implies batch processing ('multiple text segments') and hints at 'merging' (related to 'mergeOutput') and 'pacing' (related to 'pacing'), but does not elaborate on parameter interactions or semantics. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate with additional insights.

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 clearly states the tool's purpose: 'Synthesize multiple text segments with optional merging and intelligent pacing.' It specifies the verb ('synthesize'), resource ('multiple text segments'), and key optional features ('merging' and 'intelligent pacing'), making the intent unambiguous. However, it does not explicitly differentiate from sibling tools like 'synthesize_speech'—likely a batch version versus single synthesis—which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions 'optional merging and intelligent pacing,' which hints at features, but does not specify scenarios, prerequisites, or comparisons to sibling tools (e.g., 'synthesize_speech' for single segments). Without explicit when-to-use or when-not-to-use advice, the agent lacks context for tool selection.

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

Related Tools