Shoot Plan

A guide for the editor, from the plan and the takes

shoot_plan_edit_guide

Read-only

Writes the editing guide for a film, scene by scene: what each shot is for, where to cut and why, which cutaway or insert covers which jump or crossed line, the sound to lay, and each open finding as a note about what to do in the edit. With a take log it also says which take stands for each shot and marks shots that have no usable take; without one it works from the plan alone. The tools take text only, never video or audio, and no AI model runs. Input: plan; optionally takes (a dpl.takes/1 log). Output: dpl.edit-guide/1, as JSON. We don't keep the plan or the take log. Needs an agent key from a Shoot Plan account, and is free up to 3 projects a month. A project is identified by the plan's work id and title; it counts when this tool first makes a finished document for it that month. shoot_plan_allowance says what is left. Over the limit it answers ALLOWANCE_REACHED: do not retry, a new key will not help, tell your human. A fair-use limit also applies: up to 20 finished-document calls for any one project and 60 for the account each month. To count projects we keep, against your account, a one-way fingerprint (hash) of the project's id and title, the month, how many finished documents were made and when, for 13 months after the end of that month. Plans up to 8 MB and 120 calls a minute (5,000 a day).

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": {
      "plan": "<plan>"
    },
    "name": "shoot_plan_edit_guide"
  }
}

Input Schema

Name	Required	Description	Default
`plan`	Yes	The plan itself: a dpl.plan/1 JSON object (not text inside a string). Call shoot_plan_format for the schema links and an example.
`takes`	No	The take log: a dpl.takes/1 JSON object, {format, work_id, takes: [...]}. Each take has op_id, shot (the plan's shot id), kind and verdict; file names and timecodes are optional. A take log holds text about recordings: the tools take no video or audio.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes far beyond, disclosing that no AI model runs, no video/audio is accepted, the plan and take log are not retained, a hashed project fingerprint is kept for 13 months, and the exact quota mechanics (3 projects/month, 20 per project, 60 per account fair use). It also covers the failure mode precisely: 'Over the limit it answers ALLOWANCE_REACHED: do not retry, a new key will not help, tell your human' — exactly the retry guidance an agent needs.

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?

Purpose is front-loaded in the first clause and no sentence is pure filler — even the quota and retention clauses carry operational weight. It is nonetheless a single dense block that stacks purpose, limits, retention policy and rate limits together; bullets or paragraph breaks would make it faster to scan, and 'The tools take text only, never video or audio' is duplicated in the schema.

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?

With an output schema present, return-value explanation is unnecessary, and the description still covers inputs, the optional take-log path, size limits, rate limits, quota exhaustion behavior, and data-retention terms. Nothing an agent needs in order to call this correctly and interpret a failure is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real signal: the plan must be a dpl.plan/1 object (not text in a string), takes must be a dpl.takes/1 log, plans are capped at 8 MB, and shoot_plan_format is named for schema links and an example. It reinforces rather than duplicates the schema's format identifiers.

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 ('Writes the editing guide for a film, scene by scene') and then enumerates the concrete contents the guide carries (shot purpose, cut points, cutaway/insert coverage, sound, open findings as notes). That level of detail distinguishes it cleanly from siblings like shoot_plan_shoot_pack, shoot_plan_export_edit, or shoot_plan_shot_list without opening any 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?

Gives a clear conditional: 'With a take log it also says which take stands for each shot and marks shots that have no usable take; without one it works from the plan alone.' It also routes to shoot_plan_allowance for remaining quota and to shoot_plan_format for schema links. It stops short of naming a sibling alternative for a different kind of output (e.g. shoot_pack vs edit guide), so no explicit when-not-to-use.

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

All Shoot Plan tools Inspect

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

Need Help?