Shoot Plan

Make a shot list from a plan

shoot_plan_shot_list

Read-only

Turns a plan into a shot list a crew can work from. Input: plan; format, "json" (default, dpl.shot-list/1) or "markdown"; vocabulary, an optional industry vocabulary for camera terms (for example "movielabs@1.0"). Output: the shot list, or {format:"markdown", markdown}. No AI model runs. We don't keep the plan. 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_shot_list"
  }
}

Input Schema

Name	Required	Description
`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.
`format`	No	json (default) or markdown.
`vocabulary`	No	Optional industry vocabulary for camera terms, for example movielabs@1.0.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: discloses that no AI model runs, the plan is not retained, the counter is keyed on the plan's work id and title, a one-way hash with 13-month retention is stored, and there are both project/month and fair-use call caps plus 8 MB and rate limits. That is unusually rich operational disclosure for a mutation-free 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 purpose and input/output contract, and most sentences carry operational weight (limits, error handling, retention). It is a dense run-on paragraph, though, and bits like the format enumeration partly restate 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?

Given an output schema exists, the description needn't explain return values, yet it still sketches them; combined with quota, error-code, size and rate-limit coverage, an agent has everything needed to call this correctly and handle failure.

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 already 100%, so baseline is 3; the description adds real value by naming the default format and its schema id (dpl.shot-list/1), the markdown return shape {format:"markdown", markdown}, and a concrete vocabulary example (movielabs@1.0).

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 resource: turns a dpl.plan/1 plan into a shot list, with named output formats (dpl.shot-list/1 JSON or markdown). The transformation is unambiguous, but no sibling tool is named to disambiguate it from shoot_plan_shoot_pack or shoot_plan_export_for_generation.

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 clear operating context: needs an agent key, free up to 3 projects a month, and points to shoot_plan_allowance for remaining quota. It also prescribes exact behavior on ALLOWANCE_REACHED (do not retry, a new key won't help). What it lacks is guidance on when to choose this over the other plan-to-document siblings.

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?