Stormworks MCP

Overview Schema Source Related Servers Discussions Admin

preflight_vehicle

Read-onlyIdempotent

Checks a draft vehicle’s engine, driveline, and electrical connections, listing faults before saving; enable detail to view every check and repair operations.

Instructions

Check that a draft's systems are connected: engine fuel/air/exhaust/radiator paths, driveline (to wheels, or straight to a propeller on boats: no clutch or gearbox needed), electrical power and controls. By default lists only the faults, each once; detail=true adds every passing check, configuration_checks (explicit engine power), gearbox_configuration_checks, wheel_direction_checks and repair operations. A missing check's detail names what it expected and what the port does reach. Run it after wiring or routing and before saving; plan_vehicle_repairs turns its findings into fixes. Read-only; connected geometry still needs testing in game.

Input Schema

Name	Required	Description	Default
`design`	Yes	Stored draft name (from import_vehicle, create_land_vehicle, store_design or save_hull; see list_designs).
`detail`	No	true lists every check and each finding's repair operations; false (default) lists only faults, each once.

Output Schema

Name	Required	Description	Default
`checks`	Yes
`issues`	Yes
`status`	Yes
`findings`	Yes
`revision`	Yes
`wire_count`	Yes
`verification`	Yes
`missing_count`	Yes
`physical_face_pairs`	Yes
`configuration_checks`	Yes
`non_driven_wheel_faces`	Yes
`wheel_direction_checks`	Yes
`open_transmission_faces`	Yes
`capped_unused_tank_faces`	Yes
`gearbox_configuration_checks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 30, 2026

addedInput schema / properties / design / description

Added value: +"Stored draft name (from import_vehicle, create_land_vehicle, store_design or save_hull; see list_designs)."

addedInput schema / properties / detail

Added value: +{
+  "default": false,
+  "description": "true lists every check and each finding's repair operations; false (default) lists only faults, each once.",
+  "title": "Detail",
+  "type": "boolean"
+}

Addedv0.1.1Oct 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses the default output shape (faults only, each once), what detail=true expands to, that a missing check's detail names expected vs. actual connectivity, and critically that "connected geometry still needs testing in game" — an honest limit on what a pass means. Annotations only cover read-only/idempotent safety.

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 core purpose and the default output behavior, with caveats and the handoff to plan_vehicle_repairs at the end where they belong. The middle enumeration of check categories is dense but each item adds discriminating information; a small amount could be trimmed.

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 exists and annotations cover safety, so the description only needs to frame invocation and interpretation — which it does: when to run, what the default vs. detailed output means, how to read a failure, and the limits of a pass. Nothing an agent needs to call or interpret it 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 baseline is 3, but the description adds substance: detail=true is enumerated as configuration_checks, gearbox_configuration_checks, wheel_direction_checks and repair operations, not just "every check." The design parameter's provenance is left to the schema's own description.

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 (check/validate) applied to a named resource (a draft's connected systems), then enumerates the exact subsystems covered: fuel/air/exhaust/radiator paths, driveline, electrical power and controls. This is far more specific than siblings like analyze_vehicle or score_vehicle, and the parenthetical about boats with no clutch/gearbox shows domain precision.

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?

"Run it after wiring or routing and before saving" gives a clear lifecycle position, and "plan_vehicle_repairs turns its findings into fixes" routes the agent to the corrective follow-up. It does not contrast with preview_vehicle_diagnostics or prepare_vehicle_validation, so the sibling choice remains partly implicit.

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

Deploy Server