Skip to main content
Glama
macery12

Stormworks MCP

by macery12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_vehicle

Destructive

Saves a stored draft as a Stormworks vehicle XML with a Load-menu thumbnail; overwrite replaces only files it previously wrote, never imported or foreign vehicles.

Instructions

Write a stored draft into the Stormworks vehicles folder as .xml with its Load-menu thumbnail. Use it for drafts edited part by part (imports, land vehicles, edited hulls); save_hull is the shortcut for a hull spec. Refuses a name used by a vehicle this tool did not write and the imported original, even with overwrite=true; replaces its own earlier save only with overwrite=true. Returns the file path, part count and notes.

Input Schema

NameRequiredDescriptionDefault
nameYesName for the file in the vehicles folder and the game's Load menu: letters, digits, spaces, _ - ( ), at most 64 characters.
designYesStored draft name (from import_vehicle, create_land_vehicle, store_design or save_hull; see list_designs).
overwriteNoReplace an earlier vehicle of this name written by this tool. Files this tool did not write are never replaced.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • 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 / name / description
      Added value: +"Name for the file in the vehicles folder and the game's Load menu: letters, digits, spaces, _ - ( ), at most 64 characters."
    • addedInput schema / properties / overwrite / description
      Added value: +"Replace an earlier vehicle of this name written by this tool. Files this tool did not write are never replaced."
  2. Addedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotence, but the description adds the crucial policy detail: it refuses names claimed by vehicles it did not write and the imported original even when overwrite=true, and only replaces its own prior saves. It also discloses the return payload (file path, part count, notes), which is exactly the behavior an agent needs before a destructive write.

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?

Four sentences, front-loaded with the action and destination, then usage, then safety rules, then return shape — no filler. The refusal sentence is densely packed and the phrase 'the imported original' takes a moment to parse, which keeps it just shy of ideal.

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?

Given an output schema exists, the description need not detail return values, yet it summarizes them for orientation. Combined with the write policy and the part-by-part vs. hull-spec distinction, nothing an agent needs to call 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% so the baseline is 3, but the description adds real meaning to overwrite by spelling out the two-tier replacement rule (own saves vs. foreign files and the imported original). The name-collision semantics are clarified beyond the schema's shorter 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 (write a stored draft into the Stormworks vehicles folder as <name>.xml with a Load-menu thumbnail) and explicitly differentiates itself from the sibling save_hull. An agent can tell exactly what artifact this produces without inspecting the 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?

Explicitly names the use case (drafts edited part by part: imports, land vehicles, edited hulls) and the alternative (save_hull is the shortcut for a hull spec). It also states the preconditions that cause rejection, so the agent knows when the call will succeed.

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

Deploy Server

Other Tools