Stormworks MCP

Overview Schema Source Related Servers Discussions Admin

query_parts

Read-onlyIdempotent

Lists a draft's parts and current revision for exact editing, returning IDs, definitions, positions, settings, rotations, mirror bits, and transforms; call before edit_parts and pass the revision.

Instructions

List a draft's parts and its current revision for exact editing. Rows include id, definition, position, scalar settings, proper rotation plus a local mirror bitmask, and the effective transform matrix. Coordinates are integer blocks (0.25 m): the uncentred build frame for generated hulls and land drafts, the original body-local frame for imports. Call it before edit_parts and pass its revision. A selection that cuts through a multi-voxel part is rejected; select its id instead. Read-only.

Input Schema

Name	Required	Description
`limit`	No	Rows per page, 1-1000.
`design`	Yes	Stored draft name (from import_vehicle, create_land_vehicle, store_design or save_hull; see list_designs).
`offset`	No	Rows to skip, for paging; use next_offset from the previous page.
`select`	No	Filter by ids, name, definition, or inclusive bounds [[min_x,min_y,min_z],[max_x,max_y,max_z]] in blocks; omit for all parts.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / limit / description
```
Added value: +"Rows per page, 1-1000."
```
addedInput schema / properties / limit / maximum
```
Added value: +1000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

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 / select / description

Added value: +"Filter by ids, name, definition, or inclusive bounds [[min_x,min_y,min_z],[max_x,max_y,max_z]] in blocks; omit for all parts."

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 declare readOnly/idempotent, but the description adds substantive behavior: coordinate units (integer blocks, 0.25 m), two different frames depending on draft origin (uncentred build frame vs. body-local for imports), the revision token contract with edit_parts, and the selection-rejection rule. These are non-obvious constraints an agent would otherwise discover only by failure.

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 purpose and workflow, then constraints; every sentence carries information. The row-field enumeration is somewhat redundant against the output schema, keeping it just below top marks.

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 paged, read-only query with an output schema, the description covers the remaining unknowns: units, coordinate frames, the revision handoff, and the selection pitfall. Pagination is handled by the schema, so nothing an agent needs 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 baseline would be 3; the description adds real semantics on top by explaining that select can be an id selection (required for multi-voxel parts) and by introducing the revision value the caller must carry forward. It does not elaborate on limit/offset, but those are already fully documented in-schema.

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 ('List a draft's parts and its current revision') plus the intent ('for exact editing'), which separates it from search_parts and get_part_definition. The row contents are enumerated, so an agent knows exactly what it gets back.

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 explicit sequencing ('Call it before edit_parts and pass its revision') and a concrete when-not rule: a selection cutting a multi-voxel part is rejected, so select its id instead. It stops short of naming search_parts as the alternative for finding parts by criteria, so not quite a full routing guide.

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

Deploy Server