Skip to main content
Glama
Sign In
Stormworks MCP

Stormworks MCP

by macery12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_land_parts

Read-onlyIdempotent

Find installed land-build components by family, including footprints and connection ports, to choose parts for a land draft; supports search and paging.

Instructions

List installed components useful for land builds, by family, with footprints and their actual connection ports, with paging. Use it to choose parts for a land draft. search_parts covers the whole catalogue without families; get_part_definition and get_part_orientation give one part's detail. Read-only.

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, 1-200.
offsetNoRows to skip, for paging; use next_offset from the previous page.
searchNoCase-insensitive text in the definition id or display name.
categoryNoLand-build family to list; empty lists all families.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.0
    • addedInput schema / properties / category / description
      Added value: +"Land-build family to list; empty lists all families."
    • 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 / 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: +"Case-insensitive text in the definition id or display name."
  2. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the trailing 'Read-only' is mostly redundant. The description does add real context the annotations cannot: only *installed* components are listed, results include footprint and actual connection port data, and output is paged. It stops short of noting page-size caveats or ordering, but that is minor.

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?

Three tight sentences with the capability statement front-loaded ahead of alternatives. The closing 'Read-only.' duplicates annotations and is the one expendable clause.

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?

Output schema covers return values and annotations cover the safety profile, so the description only needs purpose, scope and routing — all present. Nothing an agent needs in order to call this correctly against its 50+ siblings is missing.

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%, including the category enum and the offset paging hint, so baseline is 3. The description's 'by family' phrasing implicitly maps to category and 'with paging' to limit/offset, but adds no syntax or format detail beyond the 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 installed components useful for land builds') plus the return payload (footprints and actual connection ports) and paging support. It explicitly distinguishes itself from the whole-catalogue sibling search_parts, so an agent can choose 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?

'Use it to choose parts for a land draft' gives the triggering context, and the following sentence names the alternatives and the condition that selects them: search_parts for the whole catalogue without families, get_part_definition / get_part_orientation for single-part detail.

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