Shoot Plan

Prepare a plan for image or video generation

shoot_plan_export_for_generation

Read-only

Prepares a plan for generating its pictures with a generator of your own: it returns the editorial intent of the film (eil.intent/1) and one generation brief per shot (eil.generation-briefs/1). We run no generator and receive no media: you give the briefs to your own. Input: plan; optional sequence and sequence_revision (names for the sequence the intent describes), visual_family (a term for the kind of picture the sequence is made of; the default is a_roll) and house_style (an object, for the briefs). Output: {intent, briefs}. A plan with validation errors is refused with its diagnostics. 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_export_for_generation"
  }
}

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.
`sequence`	No	Optional name for the sequence the intent describes.
`house_style`	No	Optional house style for the briefs.
`visual_family`	No	Optional visual family term; the engine lists the ones it knows if yours is not one.
`sequence_revision`	No	Optional revision label for that sequence.

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?

Discloses nearly everything an agent must know beyond the readOnlyHint annotation: no model runs, no media returned, the plan is not retained, a one-way hash of project id/title plus monthly counts is kept for 13 months, 8 MB payload cap, 120 calls/min and 5,000/day, a 3-projects-per-month allowance plus 20/60 fair-use caps, and that invalid plans are refused with diagnostics. The quota and retention disclosures are exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, which is good, but the text is one dense block of roughly 250 words and repeats itself: 'We run no generator and receive no media' is restated later as 'No AI model runs', and 'a generator of your own' is echoed by 'you give the briefs to your own'. The quota/retention paragraph is load-bearing but sprawling; it could be tightened without losing agent-critical facts.

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?

For a metered, multi-constraint tool this is thorough: auth requirement (Shoot Plan account key), quota model and what a 'project' means, non-retryable error semantics, payload and rate limits, and privacy/retention terms. An output schema exists and the description still summarizes {intent, briefs}, so nothing essential is missing before invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains all five parameters and the baseline is 3. The description adds real but limited meaning beyond it — it frames sequence/sequence_revision as names for the sequence the intent describes, house_style as shaping the briefs, and crucially gives a default the schema omits: visual_family defaults to a_roll. That default is the only genuinely new semantic detail, so it stays near baseline.

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?

Names a concrete operation (prepare a plan for generation) and the exact artifacts returned (eil.intent/1 plus one eil.generation-briefs/1 per shot), so an agent knows precisely what it gets. It also explicitly rules out what it is not: 'We run no generator and receive no media' — no sibling among export_edit, shoot_pack, or shot_list offers briefs, so the distinction is unambiguous.

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?

'you give the briefs to your own' makes the use case explicit: use this when you need generation briefs for an external image/video generator. Error-path guidance is present too ('Over the limit it answers ALLOWANCE_REACHED: do not retry... tell your human'). It never names an alternative sibling to use instead (e.g. shoot_plan_export_edit or shoot_plan_shoot_pack for other export shapes), so the routing guidance stops just short of 5.

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?