Windsock

Enrich a hull schedule (up to 100 aircraft)

enrich_hull_schedule

Run enrich_aircraft_for_underwriting over a carrier's hull schedule of up to 100 aircraft and list the insured values outside the calibrated ranges: summary.outside_range holds the aircraft insured above the central range (direction over) or below it (direction under). Each item takes the same fields as enrich_aircraft_for_underwriting (registration or make_model_id + aircraft_info.year, insured_value, reference, ...). Set book_total to true to also get the schedule's expected dollar total and a 90% range for that total, tested on held-out books (it ran wide for large mixed books and narrow for books concentrated in one segment); values without calibrated ranges (for example reference-based values) are left out and listed in book_total.excluded. Fleet Command and Enterprise API tiers only; metered per aircraft.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	The schedule: one object per aircraft, shaped like enrich_aircraft_for_underwriting's arguments.
`book_total`	No	Also return book_total: the schedule's expected dollar total and a 90% range for it, tested on held-out books (it ran wide for large mixed books and narrow for books concentrated in one segment). Default false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / book_total / description

Previous value: -"Also return book_total: the schedule's expected dollar total and a 90% range for it, tested on held-out books. Default false."New value: +"Also return book_total: the schedule's expected dollar total and a 90% range for it, tested on held-out books (it ran wide for large mixed books and narrow for books concentrated in one segment). Default false."

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / book_total

Added value: +{
+  "description": "Also return book_total: the schedule's expected dollar total and a 90% range for it, tested on held-out books. Default false.",
+  "type": "boolean"
+}

addedOutput schema / properties / data / properties / book_total

Added value: +{
+  "additionalProperties": true,
+  "description": "Present when book_total was true: available, currency, total, range {level 90, lower, upper}, sum_of_estimates, excluded[] (index, reference, reason), note; or available false with a reason.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

AddedOct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the description carries real additional weight: it discloses tier requirement, per-aircraft metering, and nuanced calibration caveats for book_total ('ran wide for large mixed books and narrow for books concentrated in one segment') plus which values are excluded. This is exactly the behavioral context an agent cannot infer from structured fields.

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 and scope are front-loaded, and every sentence carries information (item shape, book_total behavior, calibration caveats, tier/metering). It is information-dense and slightly long, but no sentence is 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?

An output schema already exists, so return formatting is covered, yet the description still clarifies summary.outside_range directions and the book_total structure with exclusions. Combined with tier, metering, and calibration notes, nothing an agent needs to invoke this correctly is 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 100%, and the schema already documents both parameters. The description goes beyond that by spelling out the shape of each item (registration or make_model_id + aircraft_info.year, insured_value, reference) and by explaining what book_total produces and how exclusions surface in book_total.excluded, adding meaning over the terse schema wording.

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 resource (enrich a carrier's hull schedule), names the scope (up to 100 aircraft), and explicitly anchors to the sibling enrich_aircraft_for_underwriting. An agent can distinguish this batch tool from the single-aircraft enrichment without opening either schema.

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 context for use — running enrichment across a whole schedule rather than one aircraft — and adds tier gating ('Fleet Command and Enterprise API tiers only') and a metering note. It stops short of an explicit 'use this instead of enrich_aircraft_for_underwriting when you have multiple aircraft' routing statement, so it is not a full 5.

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

All Windsock 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.