Shoot Plan

Convert a Shoot Plan you have bought into a DPL plan

shoot_plan_to_dpl

Read-only

Converts one of your organisation's purchased Shoot Plan plans into a dpl.plan/1 plan in the short-form profile, so you can pass it to shoot_plan_check. It is the same conversion dpl-eil's reference importer makes, and it is one way only. Input: planId (the plan's planId, spp_..., as shown inside shoot_plan_get) or taskId (the full taskId from shoot_plan_list); optionally dayStart (HH:MM, default 09:00: the clock time of minute 0 of the shoot) and date (YYYY-MM-DD). Output: {plan, report}. The report lists every field of the Shoot Plan plan that has no place in DPL or was approximated, with counts, and anything it had to assume. It also uses the structured details the plan was made from (people's names, access windows, how noisy each place is) when Shoot Plan holds them; where it does not, those come back as gaps. The private context text is never used. Read-only: the Shoot Plan plan is not changed and the DPL plan is not stored, so keep it yourself. The plan must belong to the organisation of your agent key. Needs an agent key from a Shoot Plan account, and a Shoot Plan you have bought. No AI model runs. It never counts toward the monthly allowance. Documents made from a plan you have bought do not use up a project, but they do count towards the fair-use limits. Plans up to 8 MB and 120 calls a minute (5,000 a day).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shoot_plan_to_dpl"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional shoot date, YYYY-MM-DD.
`planId`	No	The plan's planId (spp_...), as shown inside shoot_plan_get. Give this or taskId.
`taskId`	No	The taskId from shoot_plan_list. Give this or planId.
`dayStart`	No	Clock time of minute 0 of the shoot, HH:MM. Default 09:00.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: discloses that nothing is persisted, that private context text is never used, that no AI model runs, that it is free of the monthly allowance but subject to fair-use, plus concrete limits (8 MB, 120 calls/min, 5,000/day). It also explains what the report contains and where gaps surface.

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?

Purpose is front-loaded in the first clause, then inputs, output and constraints follow in a logical order with no filler sentences. It is dense and long, and the allowance/fair-use sentence is closer to marketing boilerplate than call guidance, but nothing is genuinely wasted.

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 read-only conversion with four optional params, the description covers inputs, the {plan, report} shape, fidelity caveats, auth and quota constraints. An output schema exists, yet the extra note about the report's gap listing is still useful rather than redundant.

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 100%, so the baseline is 3; the description adds locating context the schema lacks — planId comes from inside shoot_plan_get, taskId from shoot_plan_list — and clarifies dayStart semantics as the clock time of minute 0 of the shoot. The either/or relationship is stated but the default for omitted IDs is not.

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?

States a specific verb and both source and target artifacts: converts a purchased Shoot Plan into a dpl.plan/1 plan in the short-form profile, and names the downstream consumer (shoot_plan_check). This clearly separates it from siblings like shoot_plan_get (read), shoot_plan_create (authoring) and 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 real usage context: one-way conversion, result is not stored so the caller must keep it, plan must belong to the agent key's organisation, requires a purchased Shoot Plan and an agent key. It stops short of naming which alternative to pick when the caller wants a stored or editable plan (e.g. export_for_generation), so no explicit exclusions.

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?