Skip to main content
Glama

generate_speech

Converts text into AI-generated speech, creating a media pool clip and optionally placing it on the Resolve Studio timeline.

Instructions

AI text-to-speech (Resolve Studio): creates a media pool clip, optionally placed on the timeline.

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

Input Schema

NameRequiredDescriptionDefault
textYes
pitchNo
speedNo
filenameNo
variationNo
audio_trackNo
voice_modelNo
add_to_timelineNo
custom_voice_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already establish that this is a non-destructive mutation in a closed-world context, so the safety profile is known. Beyond that, the description says only that it creates a clip; it does not explain what 'AI text-to-speech (Resolve Studio)' requires, how voice_model or custom_voice_file affect behavior, or what happens if add_to_timeline is false versus true. With nine parameters at zero schema coverage, more behavioral context is needed.

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?

The description is a single front-loaded sentence with no filler, and it states the output artifact immediately. It is efficient, though its brevity contributes to the coverage gaps above.

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?

For a nine-parameter tool with no output schema and no parameter documentation anywhere else, the description is too thin. It covers the high-level effect but not the required text semantics, voice model selection, or what a successful call returns, leaving substantial gaps an agent must guess at.

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

Parameters2/5

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

Schema description coverage is 0%, and nine parameters exist, yet the description mentions only the implicit text input and the timeline-placement behavior corresponding to add_to_timeline. It adds no meaning for pitch, speed, variation, voice_model, custom_voice_file, filename, or audio_track, leaving the agent to infer everything from bare titles.

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 names a specific verb and resource ('AI text-to-speech') and its effect ('creates a media pool clip, optionally placed on the timeline'), which tells an agent what the tool produces. It is less explicit about how this differs from other clip-creation siblings like create_stereo_clip or create_compound_clip, but the core purpose is clear.

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 guidance on when to use this tool versus alternatives, no prerequisites (e.g., Resolve Studio availability), and no conditions for choosing between media-pool-only output and timeline placement. The phrase 'optionally placed on the timeline' hints at a mode but does not instruct the agent when to enable it.

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