Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_quick_tts

Convert screenplay or narration text into expressive speech with emotion control and optional voice cloning for in-IDE filmmaking workflows.

Instructions

Single-shot high fidelity speech synthesis (Higgs v3 / Qwen TTS) with emotion and optional voice cloning.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text line to speak.
emotionNoSpeech emotion tone.
voice_sampleNoOptional path to WAV reference audio for voice cloning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, yet it discloses little beyond the happy path. It does not say what the tool returns (audio file path, base64, or otherwise), whether there is a text length limit, whether voice cloning requires the referenced WAV to exist locally, or what happens on model failure — all material for a synthesis call.

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?

It is a single front-loaded sentence with the core capability first and qualifiers after, so an agent can scan it instantly. The engine parenthetical (Higgs v3 / Qwen TTS) is arguably incidental to selection and is the only mild filler.

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?

For a three-parameter tool with no annotations and no output schema, the description covers the input-side capability but leaves the result side entirely unstated — an agent cannot tell whether it receives a file, a path, or a stream. It is minimally sufficient to select the tool but not to call it with confidence about the outcome.

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%, so the schema already documents text, emotion (with its four-value enum), and voice_sample. The description reinforces that emotion is a supported control and voice cloning is optional, but adds no format, length, or fallback detail beyond the schema — the baseline of 3 is appropriate.

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 resource — 'speech synthesis' producing a single-shot utterance — and names the underlying engines (Higgs v3 / Qwen TTS). The word 'single-shot' implicitly separates it from the sibling cineflow_dialogue_tts, but that sibling is never named, so the distinction is left for the agent to infer.

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?

Usage is only implied: 'single-shot' suggests one line of text rather than a multi-speaker dialogue, and 'optional voice cloning' hints at the advanced case. There is no explicit statement of when to use this instead of cineflow_dialogue_tts, and no prerequisites or exclusions are given.

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