Skip to main content
Glama

Plan script length

plan_script_length
Read-onlyIdempotent

Use this when the user wants to fit a speech into a target duration. With a target duration and speed, returns how many words to write. With a script and target duration, returns the necessary speed plus words to cut or add at the selected pace. Target duration is 1 second to 24 hours and speed is a whole number from 60 to 300 words per minute. Numeric pause cues accept whole seconds from 1 to 86,400 per cue. Does not rewrite the script.

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": {
      "target_duration_seconds": "<target_duration_seconds>"
    },
    "name": "plan_script_length"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNoNamed writing pace or whole number from 60 to 300 wpm for the word target or cut/add estimate, e.g. conversational.
scriptNoOptional existing script to assess, e.g. Welcome everyone. Thank you for coming.
target_duration_secondsYesTarget total duration in seconds, e.g. 300 for five minutes.

Output Schema

NameRequiredDescriptionDefault
speed_wpmYes
word_changeYes
target_wordsYes
pause_secondsYes
reader_speed_wpmYes
reader_duration_msYes
necessary_speed_wpmYes
target_duration_secondsYes
necessary_speed_fractionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only, idempotent annotations, the description discloses important behavior: the tool calculates words, speed, and cut/add amounts but does not rewrite the script. It also gives duration and speed ranges and mentions pause cue constraints, which materially inform how the tool behaves.

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?

The description is front-loaded with the use case and then cleanly separates the two modes, ranges, and the explicit non-rewriting limitation. Every sentence adds useful information without redundancy.

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

Completeness5/5

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

Given rich annotations, full schema coverage, and an existing output schema, the description supplies everything an agent needs to select and invoke the tool correctly. It covers purpose, modes, bounds, and an important behavioral exclusion.

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 coverage is 100%, so the schema already documents the three parameters. The description adds some context such as whole-number speed and target duration range, but most of that repeats schema min/max constraints; the mention of numeric pause cues is extra context, though not a direct parameter in the schema.

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 planning operation with two clear modes: target duration plus speed returns a word count, while script plus target duration returns required speed and words to cut or add. This clearly identifies what the tool does, but it does not explicitly distinguish it from sibling tools such as estimate_speech_time.

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 gives a clear triggering condition: use when the user wants to fit a speech into a target duration. The two input/output modes are also described, but there is no explicit when-not guidance or naming of alternative sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources