Cut a shot plan down to what the shoot can afford
shoot_plan_fit_to_budgetCuts 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
| 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. | |
| constraints | Yes | What the shoot can afford, for example {"max_shots": 12, "max_setups": 4}. A limit left out is not a constraint. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||