Skip to main content
Glama

create_scene_plan

Read-onlyIdempotent

Calculates exact scene frame ranges from a validated timeline so each scene has defined timing before rendering.

Instructions

Calculate exact scene frame ranges from a validated 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": {
      "timeline": "<timeline>"
    },
    "name": "create_scene_plan"
  }
}

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 the safety profile is covered. The description adds that this is a pure derivation from already-validated input, implying no mutation and deterministic output, but says nothing about error behavior for invalid input or the units/format of frames returned.

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 sentence, front-loaded with the verb and deliverable, with no filler. Its terseness is efficient but leaves the description under-informative rather than padded.

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?

Because an output schema exists, the description needn't explain return values, which keeps it reasonable at this length. However, for a pipeline step with an undocumented string input, an agent still lacks the format of 'timeline' and what constitutes validation, so it is not fully complete.

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?

The single parameter has 0% schema description coverage — it is bare `timeline: string` with no documented format, encoding, or example. The description only restates that the timeline must be 'validated' without clarifying whether the string is JSON, an ID, or a path, so it fails to compensate for the schema gap.

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 output ('calculate exact scene frame ranges') and names the input ('validated timeline'), which distinguishes it from creation siblings like create_motion_scene or generate_3d_scene. It lacks any explicit naming of an alternative, so it stops short of full differentiation.

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 phrase 'from a validated timeline' implies an upstream prerequisite and thus an ordering in the pipeline, which is the only usage signal present. There is no explicit when-to-use, when-not-to-use, or reference to a sibling tool that produces or validates the timeline.

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