Stormworks MCP

Overview Schema Source Related Servers Discussions Admin

analyze_vehicle

Read-onlyIdempotent

Audit a saved Stormworks vehicle's parts, logic links, controllers, bodies, placement issues, connections, and open transmission ports section by section to debug saves or learn from builds.

Instructions

Audit how a saved vehicle is built: parts, logic links, controllers, bodies, placement issues such as rudder mounting and motion, connection candidates and open transmission ports, one section per call with paging. Use it to learn from the player's vehicles or to debug a save. Wheel layouts use analyze_land_vehicle, and hull material and floor gaps use analyze_hull. Handles multi-body vehicles. Read-only; findings are observations, not game verification.

Input Schema

Name	Required	Description	Default
`name`	Yes	Vehicle file name without .xml in the player's vehicles folder (see list_game_vehicles); with source=workshop, the numeric Steam Workshop item ID.
`limit`	No	Rows per page, 1-200.
`offset`	No	Rows to skip, for paging; use next_offset from the previous page.
`search`	No	Filter rows by text, e.g. rudder, propeller, engine or trans.
`source`	No	"vehicles" (default) reads the player's vehicles folder; "workshop" reads an installed Workshop item by numeric ID.	vehicles
`section`	No	"parts" (default), "links", "controllers", "bodies", "placement_issues", "connection_candidates" or "open_transmission_ports".	parts

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.2.0Oct 30, 2026

addedInput schema / properties / limit / description
```
Added value: +"Rows per page, 1-200."
```
addedInput schema / properties / limit / maximum
```
Added value: +200
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / name / description

Added value: +"Vehicle file name without .xml in the player's vehicles folder (see list_game_vehicles); with source=workshop, the numeric Steam Workshop item ID."

addedInput schema / properties / offset / description

Added value: +"Rows to skip, for paging; use next_offset from the previous page."

addedInput schema / properties / offset / minimum
```
Added value: +0
```

addedInput schema / properties / search / description

Added value: +"Filter rows by text, e.g. rudder, propeller, engine or trans."

addedInput schema / properties / section / description

Added value: +"\"parts\" (default), \"links\", \"controllers\", \"bodies\", \"placement_issues\", \"connection_candidates\" or \"open_transmission_ports\"."

addedInput schema / properties / source / description

Added value: +"\"vehicles\" (default) reads the player's vehicles folder; \"workshop\" reads an installed Workshop item by numeric ID."

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?

Annotations already cover the read-only/idempotent/non-destructive safety profile, yet the description still adds real behavior: results arrive one section per call with paging, multi-body vehicles are handled, and findings are explicitly observations rather than game state verification. That last caveat is a non-obvious trust signal an agent would otherwise get wrong.

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 in the first clause, with routing rules and caveats after. Slightly dense — the enumerated section list partially duplicates the schema's section enum — but every sentence still carries information.

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?

With six parameters, an output schema present, and rich annotations, the remaining burden is purpose, routing, and trust caveats — all covered. An agent can decide to call it, pick a section, and page through results without further info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so name/limit/offset/search/source/section are already fully documented, which sets the baseline at 3. The description's list of reportable areas mirrors the section parameter and adds the 'one section per call' framing, but nothing beyond that (no guidance on section ordering or search interaction).

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 ("Audit how a saved vehicle is built") and then enumerates exactly what it reports: parts, logic links, controllers, bodies, placement issues, connection candidates, open transmission ports. It explicitly distinguishes itself from two siblings by name, so an agent can separate it from analyze_land_vehicle and analyze_hull without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both selection conditions ("learn from the player's vehicles or to debug a save") and explicit routing rules to alternatives (wheel layouts → analyze_land_vehicle; hull material and floor gaps → analyze_hull). When-to-use, when-not-to-use, and the alternative are all present.

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

Deploy Server