Skip to main content
Glama

job_tts_piper

Text to speech (Piper, English voices)

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": "job_tts_piper"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesthe text to speak
voiceNovoice (default en_US-ljspeech-medium)
speakerNospeaker index (libritts_r only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the engine and language. It does not say what the tool returns (audio file, URL, base64), whether synthesis is synchronous, whether there are text-length limits, or whether voice availability is constrained to the two listed enums.

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?

A single seven-word line with the core purpose front-loaded and no filler. It is efficiently sized for what it says, though the brevity is better attributed to under-specification than to disciplined compression.

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?

This is a generative tool with no output schema and no annotations, so the description is the only place an agent could learn what comes back from a synthesis call and roughly how large an input it accepts. Neither is covered, leaving a meaningful gap for invocation planning.

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%: every parameter, including the voice enum and the speaker-index hint ('libritts_r only'), is already documented in the input schema. The description's only added semantics is confirming the voices are English, so the baseline of 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 specific verb-resource pair ('Text to speech') and adds two useful qualifiers: the engine (Piper) and the voice language (English). An agent knows immediately this synthesizes audio from text, though it does no sibling differentiation against the other job_* tools.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of when a different tool (e.g. job_transcribe, which goes the other direction) would be appropriate. The usage is only implied by the description's purpose.

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