Skip to main content
Glama
Sign In
FlowSpeech MCP Server

FlowSpeech MCP Server

by waeckerlinfederowicz66-sketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flowspeech_tts

Converts text to a WAV audio file using FlowSpeech TTS. Requires a caller-known request UUID and API key.

Instructions

Generate a WAV recording with FlowSpeech. Requires a caller-known request UUID, an API key and paid API access; consumes account credits.

Input Schema

NameRequiredDescriptionDefault
textYes
voiceNoKore
request_idYesRequired caller-known UUID. Get one with flowspeech_new_request_id; reuse only for unchanged text and voices.
output_pathNoOptional output WAV file path. An existing file is not overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / output_path / description
      Previous value: -"File path to save audio. Defaults to a timestamped file in ~/.flowspeech-mcp/audio"New value: +"Optional output WAV file path. An existing file is not overwritten."
    • addedInput schema / properties / request_id
      Added value: +{
+  "description": "Required caller-known UUID. Get one with flowspeech_new_request_id; reuse only for unchanged text and voices.",
+  "format": "uuid",
+  "type": "string"
+}
    • removedInput schema / properties / text / description
      Removed value: -"Text to convert to speech. Supports emotion stage directions inside ***(say <style>: text)***: e.g. \"***(say cheerfully: Hello!)***\""
    • removedInput schema / properties / voice / description
      Removed value: -"Voice name to use. Default: \"Kore\". Available: Puck, Fenrir, Zephyr, Autonoe, Laomedeia, Sadachbia, Leda, Aoede, Charon, Rasalgethi, Kore, Orus, Alnilam, Erinome, Iapetus, Schedar, Pulcherrima, Sadaltager, Umbriel, Callirrhoe, Achird, Zubenelgenubi, Algieba, Despina, Enceladus, Algenib, Sulafat, Vindemiatrix, Achernar, Gacrux"
    • changedInput schema / required
      Previous value: -[
-  "text"
-]New value: +[
+  "text",
+  "request_id"
+]
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well by disclosing auth needs, paid access, credit consumption, and WAV output. It still omits operational behavior such as whether generation is synchronous or job-based and how failures are surfaced.

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?

Two tight sentences with the main action and requirements front-loaded. Every clause earns its place by communicating purpose, prerequisites, or cost.

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

Completeness3/5

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

The description covers the core purpose, prerequisites, and cost, which is useful. But with no output schema, it does not explain what is returned—file path, job identifier, or otherwise—and the presence of flowspeech_get_job suggests result handling may matter.

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 50%, and the description mainly restates that a caller-known request UUID is required. It does not add meaning for text, voice, or output_path beyond what the schema already provides, so it only partially compensates for the coverage gap.

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 states a specific verb and output resource: generate a WAV recording with FlowSpeech. It is clear what the tool does, but it does not distinguish this single-recording tool from the sibling flowspeech_tts_multi.

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?

It gives prerequisites—caller-known request UUID, API key, paid API access, and credit consumption—which helps determine whether the tool is usable. However, it does not say when to choose this over flowspeech_tts_multi or how to obtain the UUID without relying on the schema.

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