Skip to main content
Glama

generate_voiceover_script

Read-onlyIdempotent

Creates a timed script from client-authored, evidence-bound scene copy, preserving the provided language.

Instructions

Create a timed script from client-authored evidence-bound scene copy; preserves provided language.

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": {
      "timeline": "<timeline>"
    },
    "name": "generate_voiceover_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds one real behavioral trait beyond that — 'preserves provided language', i.e. no translation or localization — plus the implication that timing is computed rather than supplied. It says nothing about what timing model or constraints are applied.

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?

One dense sentence with no filler, front-loaded with the verb and output artifact. The semicolon clause adds a distinct constraint rather than restating, so length is justified — though the compressed noun phrases cost readability.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. What remains missing is essential for correct invocation: the meaning and expected format of 'timeline' and the relationship to generate_voiceover downstream.

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 coverage is 0% for the single required parameter 'timeline', so the description carries the full burden and does not meet it. It never connects 'timeline' to the described 'scene copy' or 'timed script', leaving ambiguous whether timeline is the raw copy, a structured scene list, or a timing manifest.

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 and artifact ('Create a timed script') from a specific input ('client-authored evidence-bound scene copy'), which separates it from generate_voiceover (audio) in the sibling list. The qualifiers 'evidence-bound' and 'timed' are undefined jargon, slightly blunting the clarity.

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?

The description implies a prerequisite input (client-authored, evidence-bound scene copy) but never states when to call this versus generate_voiceover or create_scene_plan, nor what to do if the copy is not 'evidence-bound'. No exclusions, no sequencing guidance.

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