Skip to main content
Glama
macery12

Stormworks MCP

by macery12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

preview_interior

Read-onlyIdempotent

Render a labelled interior cutaway, deck plans for each room level, and a per-room report to inspect clear sizes, doors, floor steps, and engines after adding an interior spec; nothing is written.

Instructions

Render an interior cutaway: a centreline section plus a labelled deck plan for every room level, and a per-room report (clear size, floor width, doors with sill heights and floor steps, engines, warnings). Use it after adding interior to a spec (hull_design_guide topic=interior); preview_hull shows the outside. Floors above the main deck are cropped to their rooms. Nothing is written.

Input Schema

NameRequiredDescriptionDefault
specNoHull spec, partial or full (fields: hull_design_guide topic=spec); merged over preset or design. Lengths in metres.
patchNoJSON-Patch ops applied last, e.g. [{"op": "replace", "path": "/superstructure/bridge/height", "value": 2.5}]; list items can be named instead of indexed.
designNoStored design to start from instead of a preset; names from list_designs.
presetNoBuilt-in hull preset to start from, e.g. 'runabout'; names from list_hull_presets.
spec_pathNoPath to a .json file holding a spec or a stored design, read before spec and patch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • addedInput schema / properties / design / description
      Added value: +"Stored design to start from instead of a preset; names from list_designs."
    • addedInput schema / properties / patch / description
      Added value: +"JSON-Patch ops applied last, e.g. [{\"op\": \"replace\", \"path\": \"/superstructure/bridge/height\", \"value\": 2.5}]; list items can be named instead of indexed."
    • addedInput schema / properties / preset / description
      Added value: +"Built-in hull preset to start from, e.g. 'runabout'; names from list_hull_presets."
    • addedInput schema / properties / spec / description
      Added value: +"Hull spec, partial or full (fields: hull_design_guide topic=spec); merged over preset or design. Lengths in metres."
    • addedInput schema / properties / spec_path / description
      Added value: +"Path to a .json file holding a spec or a stored design, read before spec and patch."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description reinforces that with 'Nothing is written.' Beyond the annotations it adds genuine behavioral detail: what the rendered output contains and the cropping rule for floors above the main deck. It does not cover cost/performance or output format, which keeps it below 5.

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 action and output, followed by usage and a caveat; three sentences with little waste. The middle parenthetical listing report contents is dense but earns its place. Minor redundancy between 'Nothing is written' and the readOnly annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing what the preview and report contain, including the per-room fields and the main-deck cropping behavior. Adequate for a zero-required-parameter preview tool; only the concrete return medium (image vs. text report) is left implicit.

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% and each parameter is documented in the schema, so the baseline is 3. The description adds no parameter-level meaning beyond referring readers to hull_design_guide for spec fields; it neither explains merge precedence (schema covers) nor lists presets/designs in text.

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 (render) and resource (interior cutaway) and enumerates exactly what is produced: a centreline section, a labelled deck plan per room level, and a per-room report with named fields. It explicitly separates itself from preview_hull ('shows the outside'), so an agent can distinguish the two without opening either schema.

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 a clear precondition ('use it after adding `interior` to a spec') and points at the guide topic that produces that input. It also names the relevant alternative, preview_hull, and what it covers. It stops short of stating when not to use it (e.g. when a spec has no interior), so not a full 5.

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