Skip to main content
Glama
valentinlutun-cmd

Voicebox MCP (Full)

voicebox_generate

Generate speech from text using a voice profile. Returns an ID to poll for generation status.

Instructions

Generate speech from text using a voice profile.

Returns a GenerationResponse with status="generating" and an id to poll at voicebox_get_generation_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoReproducible seed (null = random).
textYesText to speak (max 50000 chars).
engineNoTTS engine — qwen, qwen_custom_voice, luxtts, chatterbox, chatterbox_turbo, tada, kokoro.qwen
instructNoOptional instruction prompt (max 500 chars).
languageNoLanguage code — en, zh, ja, ko, de, fr, ru, pt, es, it, he, ar, da, el, fi, hi, ms, nl, no, pl, sv, sw, tr.en
normalizeNoNormalize output audio volume.
model_sizeNoModel size — 1.7B, 0.6B, 1B, 3B.1.7B
profile_idYesVoice profile ID (use voicebox_list_profiles to find).
personalityNoWhen true, rewrites text in-character before TTS.
crossfade_msNoCrossfade between chunks in ms (0-500).
max_chunk_charsNoMax chars per chunk for long text (100-5000).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It correctly notes the async nature and the polling mechanism, but does not disclose side effects, required permissions, or error recovery. This is adequate but not comprehensive for a mutation tool.

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 two sentences with no wasted words. The first sentence states the core purpose; the second explains the return value and next step. Perfectly front-loaded and concise.

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?

Given the tool's complexity (11 parameters, async generation) and the existence of an output schema, the description provides the essential workflow. It could be enhanced by explaining common parameter combinations or failure handling, but it is largely complete for a description paired with a rich schema.

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% with detailed descriptions for all 11 parameters. The description adds only the context 'using a voice profile,' which maps to profile_id, but this is minimal extra value. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates speech from text using a voice profile, and distinguishes itself by mentioning the asynchronous polling pattern via an ID—this differentiates it from synchronous or other generation tools.

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?

The description implies that after calling this tool, one should use voicebox_get_generation_status to poll, but it does not explicitly state when to use this versus alternative generation tools like voicebox_speak or voicebox_regenerate. The agent lacks guidance on selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/valentinlutun-cmd/voicebox-mcp-full'

If you have feedback or need assistance with the MCP directory API, please join our Discord server