Skip to main content
Glama
Sign In

framesail

by com.framesail
OverviewDiscussions(1)Admin

Generate the voiceover

voiceover_generate
Destructive

Generate voice block audio. Every speaker needs a voice first, and every asset a reference image. Without voice_block_ids it fills every block with no audio, skipping ones already generating. A model must match the project's voice engine. An existing storyboard retimes to the new audio on its own.

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": {
      "project_id": "<project_id>"
    },
    "name": "voiceover_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel id (get_generation_options); omit for the saved choice
dry_runNoReturn the count and credit estimate; start nothing
settingsNoModel settings: keys of its settings_schema
project_idYesProject id
voice_block_idsNoBlocks to generate, again if they have audio; omit for every block without audio
editable_sectionsNoTemplate prompt section overrides, keyed by section id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds genuinely new behavior: silent skipping of blocks already generating, the model/voice-engine compatibility constraint, and the side effect that an existing storyboard retimes automatically. It omits cost/credit and async/status implications, which matter for a destructive generate 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?

Short and front-loaded: the core action comes first, then prerequisites, then edge behaviors. The telegraphic fragments ('Every speaker needs a voice first') read as clipped notes, but no sentence is wasted.

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 destructive, non-idempotent generation tool with no output schema, the description covers prerequisites and one side effect well. It leaves out whether the call is asynchronous (needing get_status) and what is returned, which are real gaps for an agent deciding how to proceed.

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 every parameter is already documented, including voice_block_ids and dry_run. The description restates the voice_block_ids default and mentions the model-must-match rule, but adds little beyond the schema on settings, editable_sections, or dry_run.

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?

Opens with a specific verb and resource ('Generate voice block audio'), which separates it cleanly from voiceover_read and voiceover_edit in the sibling list. It does not name siblings explicitly, but the generate/read/edit triad makes the distinction obvious.

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?

It states the default selection rule ('Without voice_block_ids it fills every block with no audio, skipping ones already generating') and the prerequisites ('Every speaker needs a voice first, and every asset a reference image'), so an agent knows when this call is valid. It never says when to prefer dry_run or how this differs from storyboard_generate, so it doesn't reach 5.

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

All framesail toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources