Skip to main content
Glama

Make the shoot-day pack from a plan

shoot_plan_shoot_pack
Read-only

Makes the pack to take on the shoot day: the call sheet with, for each scene, its shots, the action, the look and the sound notes. Use it when the crew needs one document to work from; use shoot_plan_call_sheet when only the times and people are wanted. Input: plan, a dpl.plan/1 object that validates; optionally day, the id of one day in the plan's schedule (a day the plan does not have is refused, and the refusal lists the days it has). Output: dpl.shoot-pack/1. 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_shoot_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoOptional: the id of one shoot day in the plan's schedule, for example day1. Leave it out for the whole schedule.
planYesThe plan itself: a dpl.plan/1 JSON object (not text inside a string). Call shoot_plan_format for the schema links and an example.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description provides extensive behavioral context far beyond the basic annotations. It discloses critical operational facts: no AI model runs, no plans are stored, specific authentication requirements (Shoot Plan account key), and detailed rate limits (3 projects/month, 20/60 call limits). This is crucial operational knowledge.

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?

The description is excessively long, which hurts conciseness. However, due to the high complexity of the tool (rate limits, operational constraints, technical specs), the necessary information is logically segmented, even if not brief.

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 the tool's operational complexity (limits, fingerprinting, technical throughput), the description is extremely complete. An agent needs all this information—especially the resource constraints and error states—to use the tool successfully and ethically.

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?

While the schema coverage is 100%, the description adds vital clarity regarding parameter logic. Specifically, it explains the 'day' parameter's optional nature—it's an ID for a specific day, and omitting it applies to the entire schedule, which informs the agent's invocation logic.

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 clearly defines the tool's purpose: creating a comprehensive 'shoot-day pack' containing specific notes (shots, action, look, sound). It provides excellent differentiation by stating that 'shoot_plan_call_sheet' should be used when only times and personnel are needed, avoiding sibling confusion.

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 provides explicit instructions on when and how to use the tool versus alternatives. It sets operational limits (3 projects/month) and defines specific responses to resource exhaustion (i.e., 'ALLOWANCE_REACHED'), which guides the agent's subsequent behavior.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources