Skip to main content
Glama

flow_storyboard_plan

Define an ordered shot list with prompts, actions, durations, camera moves, dialogue, and sound before any media is generated; choose replace, append, or reset to control the plan.

Instructions

Set the storyboard: an ordered list of shots. Nothing is generated yet.

Each shot is an object with: prompt (required): what we see: subject, place, light. Use @name for ingredients. action: what moves or happens during the shot. duration: seconds, 3-15 (default 5). camera: a camera preset ('push-in', 'orbit', 'drone', ...) or your own words. dialogue: spoken line(s), e.g. 'Mira says: "We made it."' sound: sound design, e.g. 'soft rain, distant thunder, no music'. ingredients: extra ingredient names to attach besides the @tags.

Args: shots: The shot list. mode: 'replace' (default; refuses if existing shots already have keyframes or takes), 'append' (add to the end) or 'reset' (drop the old plan; files stay on disk). project_name: Project to use (default: active project).

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": {
      "shots": "<shots>"
    },
    "name": "flow_storyboard_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoreplace
shotsYes
project_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does well: it discloses that nothing is generated, that 'replace' fails under specific preconditions (existing keyframes or takes), that 'reset' drops the plan while leaving files on disk, and that 'append' adds to the end. It does not describe what happens to previously referenced files or shots under 'replace', which is the remaining gap for a mutation tool.

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?

Front-loaded with the purpose, then structured as an indented field list followed by an Args section, so it scans well. There is minor duplication between the shot-field list and the Args entry for 'shots', but every line carries usable information and nothing is padding.

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 a 3-parameter tool with a free-form nested object, no annotations, and no output schema, the description supplies everything an agent needs: the shape of each shot, defaults and ranges, mode side effects and failure conditions, and project targeting. No structural field is left undocumented.

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

Parameters5/5

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

Schema description coverage is 0% and the shots array is only typed as a generic object with additionalProperties, yet the description fully specifies the shot record (prompt required, action, duration 3-15 default 5, camera presets, dialogue, sound, ingredients), the @name ingredient syntax, and the three mode behaviors. This adds substantial meaning that the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Set the storyboard: an ordered list of shots') and immediately delimits scope with 'Nothing is generated yet', which separates it from the flow_generate_* and flow_storyboard_render siblings. An agent knows this is the planning step before generation without opening the schema.

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?

Usage context is clear (planning precedes keyframes/render) and the mode parameter encodes when-to-use rules: 'replace' is the default but refuses when existing shots already have keyframes or takes, which implicitly routes the agent to 'append' in that case. It stops short of naming the follow-up sibling tools explicitly, so there is no full alternatives map.

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