Shoot Plan

A short account of a plan, for when context is short

shoot_plan_summary

Read-only

Gives a short account of a plan, about 300 words, so that you can pick the work up again without being sent the whole plan: the title, the planned runtime against the target, the counts of scenes, shots, characters and places, the thesis and journey, one line for each sequence and scene, the missing-details counts, and, if you pass the check result, the open findings by severity. Fetch it first when you come back to a film. The scene ids it lists are the ones to ask shoot_plan_slice for. Input: plan, a dpl.plan/1 object; optionally findings, the dpl.findings/1 document shoot_plan_check returned for this plan (without it the summary says no findings were given and does not run the checks; if they are for another revision of the plan, it says so). Output: dpl.summary/1. A plan that does not validate is refused with its diagnostics. No AI model runs. We don't keep the plan. We log a one-way fingerprint (hash) of it, its size, the tool, the type of client, the result and the time taken. Needs an agent key from a Shoot Plan account. Free, and it does not count toward the account's 3 free projects a 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_summary"
  }
}

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.
`findings`	No	Optional: the dpl.findings/1 document shoot_plan_check returned for this same plan, exactly as returned.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses no AI model runs, no plan retention, a logged one-way fingerprint/hash plus size, tool, client type, result and time taken, the need for an agent key, that it is free and exempt from the 3-free-projects limit, and hard limits of 8 MB and 120 calls/min (5,000/day). It also states failure behavior: invalid plans are refused with diagnostics. These are substantive behavioral details annotations cannot convey.

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?

It is a long description, but it is front-loaded with purpose and every sentence carries distinct, useful information: contents, usage, input behavior, output type, failure mode, privacy, authentication, pricing and limits. Nothing is redundant, and the ordering moves from what to when to operational constraints.

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?

Although an output schema exists (so return values needn't be explained), the description still enumerates the summary contents for quick comprehension. With only two parameters, 100% schema coverage, and rich annotations, the description completes the picture by covering error behavior, data handling, auth, rate limits and findings semantics.

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 coverage is 100%, so a baseline of 3 would apply, but the description adds real meaning: it clarifies that plan is a dpl.plan/1 object (not a string), that findings must be the exact dpl.findings/1 document returned by shoot_plan_check, and what happens if findings are missing or for another revision. That goes well beyond the schema's own descriptions.

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?

The description opens with a specific verb and resource — 'Gives a short account of a plan, about 300 words' — and then enumerates exactly what the account contains (title, runtime vs. target, counts, thesis/journey, per-sequence/scene lines, missing-details counts, findings). It implicitly distinguishes itself from retrieving the whole plan ('without being sent the whole plan'), so an agent can immediately tell this is the condensed-read tool rather than shoot_plan_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('Fetch it first when you come back to a film') and when to omit the optional findings input ('without it the summary says no findings were given and does not run the checks'). It also names the relevant siblings — shoot_plan_check for the findings document and shoot_plan_slice for the scene ids — leaving little to inference.

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?