Windsock

Create a verified valuation report

create_valuation_report

Generate a full Windsock verified value report (contemporary model only) from the same inputs as the windsock.ai valuation wizard. Creates a durable report owned by your account and queues PDF generation. Send the tail AND everything you know about the aircraft: any aircraft_info field you omit is filled with the make/model cohort MEDIAN, so a report built from a year alone prices like an average example — the response's inputs.stats_imputed / inputs.year_imputed list what was filled. Requires Windsock PRO or Enterprise.

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

Input Schema

Name	Required	Description
`folder`	No	Optional folder label (max 80 chars).
`purpose`	No	Why the valuation is needed (e.g. buy, sell, financing, insurance).
`adjustments`	No	STC / custom modification value adjustments (USD), as in the wizard. NOT model inputs: stored on the report and added on top of the model estimate (final_estimate).
`avionics_ids`	No	Installed avionics, as ids from search_avionics. A model input — affects the price.
`registration`	No	Tail number. Always send it when known — with or without make_model_id — so the registry year and location are used and the report carries the tail.
`aircraft_info`	No	Aircraft specs (overrides when a tail is given). Same shape and scale rules as value_aircraft's aircraft_info — in particular, a literal quality grade of 1 reads as like-new; send 0.1 for the worst. Omitted fields are imputed from the make/model cohort median.
`make_model_id`	No	FAA make/model id (from search_make_models). Optional when a registration is given (resolved from the registry).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

addedOutput schema / properties / data / properties / generation_deferred_until

Added value: +{
+  "description": "Present only while PDF rendering is rescheduled because every renderer was busy: when the deferred render is due. The report is queued, not stuck.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / data / properties / retry_after_seconds

Added value: +{
+  "description": "Present with generation_deferred_until: seconds until it is worth polling again.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed12 schema fields changedOct 1, 2026

addedInput schema / properties / adjustments

Added value: +{
+  "description": "STC / custom modification value adjustments (USD), as in the wizard. NOT model inputs: stored on the report and added on top of the model estimate (final_estimate).",
+  "items": {
+    "properties": {
+      "description": {
+        "description": "Required for type=custom.",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "stc_holder": {
+        "type": "string"
+      },
+      "stc_id": {
+        "description": "STC id (from search_stcs), for type=stc.",
+        "type": "integer"
+      },
+      "type": {
+        "enum": [
+          "stc",
+          "custom"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "description": "Dollar adjustment (negative allowed).",
+        "type": "number"
+      }
+    },
+    "required": [
+      "type",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / aircraft_info / description

Previous value: -"Same shape and scale rules as value_aircraft's aircraft_info — in particular, a literal quality grade of 1 reads as like-new; send 0.1 for the worst."New value: +"Aircraft specs (overrides when a tail is given). Same shape and scale rules as value_aircraft's aircraft_info — in particular, a literal quality grade of 1 reads as like-new; send 0.1 for the worst. Omitted fields are imputed from the make/model cohort median."

addedInput schema / properties / aircraft_info / properties / aftt

Added value: +{
+  "description": "Airframe total time (hours).",
+  "type": "number"
+}

addedInput schema / properties / aircraft_info / properties / lat

Added value: +{
+  "description": "Aircraft base latitude. Defaults to the registered/last-seen location when a tail is given.",
+  "type": "number"
+}

addedInput schema / properties / aircraft_info / properties / lon

Added value: +{
+  "description": "Aircraft base longitude.",
+  "type": "number"
+}

addedInput schema / properties / aircraft_info / properties / smoh_1

Added value: +{
+  "description": "Hours since major overhaul, engine 1.",
+  "type": "number"
+}

addedInput schema / properties / aircraft_info / properties / smoh_2

Added value: +{
+  "description": "Hours since major overhaul, engine 2 (ignored for single-engine aircraft).",
+  "type": "number"
+}

addedInput schema / properties / avionics_ids

Added value: +{
+  "description": "Installed avionics, as ids from search_avionics. A model input — affects the price.",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

addedInput schema / properties / folder

Added value: +{
+  "description": "Optional folder label (max 80 chars).",
+  "type": "string"
+}

addedInput schema / properties / make_model_id / description

Added value: +"FAA make/model id (from search_make_models). Optional when a registration is given (resolved from the registry)."

addedInput schema / properties / purpose

Added value: +{
+  "description": "Why the valuation is needed (e.g. buy, sell, financing, insurance).",
+  "type": "string"
+}

addedInput schema / properties / registration / description

Added value: +"Tail number. Always send it when known — with or without make_model_id — so the registry year and location are used and the report carries the tail."

First observedSep 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true; the description goes well beyond them by disclosing that a durable account-owned report is created, that PDF generation is queued asynchronously, that omitted aircraft_info fields are imputed with the cohort median, and that the response exposes inputs.stats_imputed / inputs.year_imputed. The entitlement prerequisite (PRO/Enterprise) is also surfaced, which annotations cannot convey.

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?

Front-loaded with the purpose, then the durability/PDF behavior, then the imputation warning and the entitlement requirement. Every sentence carries information, though the imputation explanation is compressed into one long clause and the 'same inputs as the windsock.ai valuation wizard' framing adds little for an agent.

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 create-a-durable-artifact tool with 7 nested parameters and an output schema, the description covers what is created, the side effect (queued PDF), the entitlement gate, the imputation risk, and which response fields report imputation. Nothing essential to correct invocation 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%, so the schema already documents every field and the baseline is 3; the description still adds genuine meaning by explaining the imputation semantics of omitted aircraft_info fields (filled with make/model cohort median) and by instructing the agent to always send the tail. It stops short of explaining how registration and make_model_id interact beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Generate a full Windsock verified value report') and scopes it ('contemporary model only'), and the phrase 'Creates a durable report owned by your account and queues PDF generation' implicitly separates it from the ephemeral sibling value_aircraft. It never names value_aircraft or any other sibling explicitly, so the differentiation is inferred rather than stated.

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 concrete context for use: send the tail plus all known aircraft_info, and notes two hard constraints ('contemporary model only', 'Requires Windsock PRO or Enterprise'). It does not tell the agent when to prefer this over the value_aircraft sibling, leaving the report-vs-instant-valuation choice to inference.

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.