Skip to main content
Glama

make_voice

Convert text into an audio voice line for add_voice. Choose the free online engine with word timings for captions, or the offline engine to clone a voice from a short recording.

Instructions

A voice line from text, as an audio file for add_voice. engine "edge" (default): free online voices, fast, with word timings for auto captions; voice: andrew, emma, ava, brian, es, es-f, pt, pt-f, or any edge voice name. engine "local": Chatterbox on this PC, offline, CLONES the voice in sample (a 5-15 s recording); slow.

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": {
      "text": "<text>"
    },
    "name": "make_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
voiceNoandrew
engineNoedge
sampleNo
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses that 'edge' is an online service (consistent with openWorldHint), that 'local' runs on this PC, is slow, and requires a 5-15 second sample to clone. It also mentions word timings returned for auto captions. It omits run time, output file location, and failure modes for a bad sample.

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?

Two compact sentences, front-loaded with the output and its destination before the engine detail. Slightly dense and the mid-sentence line break hurts readability, but no sentence is padding.

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?

For a five-parameter generative tool with no output schema and only hint-level annotations, the description covers the engine choice, voice options, sample requirement, and output usage. Minor absences: the 'language' parameter, output file format, and expected latency/credits for the online engine.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameters, and it does for most: text (implied by the purpose), voice (concrete defaults plus 'any edge voice name'), engine (both values with defaults), and sample (5-15 s recording constraint). Only 'language' is left unexplained, which is the sole meaningful gap across five params.

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?

States a specific verb and resource ('A voice line from text, as an audio file') and names the downstream consumer ('for add_voice'), so the agent knows this is a text-to-speech generator whose output feeds the voice-adding step. That is clearly distinct from the many video-editing siblings.

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?

The engine split functions as real when-to-use guidance: 'edge' for free, fast online voices with word timings; 'local' for offline, slower cloning from a sample recording. It does not explicitly say 'use this instead of X', but the decision criteria for the main fork are spelled out.

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