Skip to main content
Glama

Cut a shot plan down to what the shoot can afford

shoot_plan_fit_to_budget
Read-only

Cuts a plan down to what the shoot can afford, without dropping a shot marked must: it takes out the least necessary shots one at a time, re-checking the plan after each, and tells you what each cut costs. Input: plan, and constraints: max_shots (the most shots the cut may need) and/or max_setups (the most camera set-ups; shots sharing a set-up count once). The engine refuses any other limit and says which it takes. Output: dpl.replan/1 with met (true or false; false says which limit failed, by how much and what to relax), the sacrifices, and the revised plan with its findings. Not meeting a limit is an answer, not an error. It can take several seconds on a large plan (up to 30 s here). No AI model runs; nothing is stored. 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>",
      "constraints": "<constraints>"
    },
    "name": "shoot_plan_fit_to_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
constraintsYesWhat the shoot can afford, for example {"max_shots": 12, "max_setups": 4}. A limit left out is not a constraint.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint=true and openWorldHint=false, the description adds substantial behavioral context: iterative removal with re-checking, per-cut cost reporting, non-error status when a limit is not met, runtime up to 30 seconds, no AI model, no storage, authentication requirements, free usage, and size/rate limits. This is unusually complete disclosure.

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?

The description is dense and front-loaded with the core action and invariant before operational details. It is somewhat long and packs many clauses into single sentences, but nearly every sentence earns its place by covering output, errors, constraints, runtime, auth, and limits.

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 a complex planning operation with nested objects, an output schema, and only two parameters, the description covers the action, constraints, refusal behavior, output shape, non-error semantics, runtime, authentication, and quotas. Nothing an agent needs in order to call it correctly appears to be 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 already 100%, but the description adds useful semantics for the constraints: `max_shots` as the most shots the cut may need, and `max_setups` with the rule that shots sharing a set-up count once. It does not add detail about the `plan` object format beyond pointing to the schema indirectly, so it is strong but not maximally informative.

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 states a specific verb and resource: cutting a shot plan down to an affordable size while preserving shots marked `must`. It makes the transformation and its key invariant unmistakable, so an agent can distinguish it from siblings like shoot_plan_slice or shoot_plan_revise.

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?

It clearly explains the input limits (`max_shots` and/or `max_setups`) and that the engine accepts no other limit, which tells the agent when this tool applies. It does not explicitly name alternative tools for related planning operations, so it falls short of full when/when-not routing.

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