Skip to main content
Glama
macery12

Stormworks MCP

by macery12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hull_design_guide

Read-onlyIdempotent

Read Stormworks boat design guidance in Markdown by topic—workflow, units, specs, style, limits, building, and testing—to plan hulls before building.

Instructions

Return the boat design guide as Markdown: workflow, units, every spec field, style rules and lessons from in-game testing. Read topic="workflow" before designing a boat, then fetch focused topics as needed instead of resending the full guide. Road and land vehicles have their own guide (land_vehicle_guide). Read-only.

Input Schema

NameRequiredDescriptionDefault
topicNoSection to return: full (everything), workflow (start here), units, spec (every field), interior, archetypes (starting proportions), style, limits, staged (staged builder), building and edits (building step by step, exact edits), testing (what is verified in game), smoothing (wedge skins), topics (list the topics).full

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / topic / description
      Added value: +"Section to return: full (everything), workflow (start here), units, spec (every field), interior, archetypes (starting proportions), style, limits, staged (staged builder), building and edits (building step by step, exact edits), testing (what is verified in game), smoothing (wedge skins), topics (list the topics)."
  2. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / topic
      Added value: +{
+  "default": "full",
+  "enum": [
+    "full",
+    "workflow",
+    "units",
+    "spec",
+    "interior",
+    "archetypes",
+    "style",
+    "limits",
+    "staged",
+    "building",
+    "testing",
+    "smoothing",
+    "edits",
+    "topics"
+  ],
+  "title": "Topic",
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, and the description reinforces read-only while adding that the return is Markdown. It also explains the efficiency behavior of fetching focused topics rather than repeatedly retrieving the full guide. The remaining behavioral gaps are minor because the safety profile is already covered by annotations and the return shape is covered by an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with what is returned, then usage guidance, then the sibling alternative. Every sentence contributes practical routing or invocation information with no filler.

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 single-parameter documentation retrieval tool with an output schema, the description provides what it returns, the recommended topic strategy, and the relevant alternative tool. Nothing essential for correct invocation 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 enum values are already well documented. The description still adds procedural meaning by identifying workflow as the starting topic and focused topics as the preferred alternative to full, which helps an agent choose parameter values in context.

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?

The description uses a specific verb and resource: return the boat design guide as Markdown. It explicitly distinguishes this guide from the separate road/land vehicle guide by naming land_vehicle_guide, so an agent can route correctly without inspecting schemas.

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?

It gives explicit sequencing guidance: read topic="workflow" before designing a boat, then fetch focused topics as needed instead of resending the full guide. It also names the alternative for road and land vehicles, leaving little ambiguity about when to use this tool versus land_vehicle_guide.

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