Whirrwork

Drone light show cost

estimate_drone_show_cost

Read-onlyIdempotent

Cost of a drone light show of N drones: every published per-drone price x drones (best match for the country first, peak-date prices only when peak=true), plus the published whole shows closest in drone count (NEVER scaled to your size; implied per drone = show price / stated drones), the same-country span, a check of a quote the buyer received (per drone vs the published range in that currency) and too_few_receipts when fewer than 3 prices apply to the country. Every price has source_url and as_of. Same maths as whirrwork.com/tools/drone-show-cost/. Currencies are NEVER converted. Not a quote and not a Whirrwork estimate: say so. Examples: {"drones":200,"country":"US"}; {"drones":100,"country":"GB","quote":9000,"currency":"GBP"}; {"drones":500,"country":"CN"}.

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": "estimate_drone_show_cost"
  }
}

Input Schema

Name	Required	Description
`peak`	No	Peak date (e.g. July 4th, New Year's Eve): include peak-date prices
`quote`	No	Total price the buyer was quoted, to check against published prices
`drones`	No	Number of drones in the show
`country`	No	Buyer country, ISO 3166-1 alpha-2
`currency`	No	Currency of quote (ISO 4217)
`language`	No	Language for use-case text (machine-translated; English is authoritative). Default en.

Output Schema

Name	Required	Description
`job`	No
`url`	Yes
`peak`	No
`tool`	Yes
`input`	No
`label`	No
`drones`	No
`method`	No
`prices`	Yes
`country`	No
`formula`	Yes
`version`	No
`language`	No
`selected`	No	Best-matching per-drone price applied to your drone count (null when none applies)
`your_quote`	No
`too_few_receipts`	No
`same_country_span`	No
`countries_with_prices`	No
`nearest_published_shows`	No
`receipts_for_your_country`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only annotations, it discloses important behavior: prices are never currency-converted, whole-show prices are never scaled, too_few_receipts is returned with fewer than 3 country prices, and every price has source_url and as_of. It also explicitly says the result is not a quote or Whirrwork estimate, which prevents misinterpretation.

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 front-loaded with the core purpose and is appropriately detailed for a cost-estimation tool with several behavioral rules. It is somewhat dense and run-on, with all-caps emphasis, but most sentences carry necessary methodological information rather than filler.

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 output schema, annotations, and six parameters, the description is complete enough for an agent to invoke it correctly. It covers calculation method, caveats, currency handling, quote checks, and the explicit warning that the result is not a quote, leaving little ambiguity.

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?

Although schema coverage is already 100%, the description adds meaningful semantics for key parameters: country is matched to published per-drone prices first, peak controls peak-date price inclusion, and quote is checked against the published range in the given currency. It also clarifies that currency is never converted, which is important for interpreting the quote parameter.

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 resource and calculation: the cost of a drone light show with N drones, including country matching and quote checks. It clearly differentiates this from the sibling estimate_drone_spraying_cost by domain and from generic cost tools by the drone-light-show-specific methodology.

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 gives clear usage context: peak-date prices only when peak=true, quote checking when a quote is supplied, and country-first matching. It does not explicitly name alternative sibling tools or when not to use this one, but the domain and examples make the intended use clear.

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

All Whirrwork 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?