Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

commission_status

Read-onlyIdempotent

Check the status of your ship commissions (Shows all your active commissions, including whether each order is a bare hull or default fit and whether it uses partial sourcing. On sourcing entries, required_materials is the total requirement, materials_gathered is cumulative and already includes materials_initially_supplied plus later donations and yard purchases, and materials_to_source is the remaining deficit: max(required_materials - materials_gathered, 0) per item. Omitted map keys and omitted materials_to_source items mean zero. Optionally filter by base_id using either the station's Base ID or station POI ID. Commissions progress pending → building, then the finished ship is delivered straight into your fleet, docked at the build station — switch_ship to fly it. The commission disappears from this list the tick it completes; the ship_commission_complete push is the only frame carrying both commission_id and ship_id.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idNoOptional: filter commissions to a station by either its Base ID or station POI ID
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / base_id / description
      Previous value: -"Optional: filter commissions to a specific base"New value: +"Optional: filter commissions to a station by either its Base ID or station POI ID"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description aligns with those by describing a read-only status query. It adds substantial behavioral detail beyond the annotations: field semantics for materials, omitted keys meaning zero, the pending→building lifecycle, delivery into the fleet, and the commission disappearing from the list once complete.

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?

The core purpose is front-loaded, and every included detail is useful, especially because there is no output schema to carry return-value semantics. The description is dense and slightly unwieldy as one large parenthetical block, but it earns its length by documenting edge cases and lifecycle behavior.

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?

With no output schema present, the description compensates thoroughly by explaining the meaning of key response fields, zero-value omissions, base_id filtering, lifecycle progression, and the completion signal. For a status-checking tool with read-only annotations, this is complete enough for an agent to call and interpret the result correctly.

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%, so the schema already documents both session_id and base_id. The description repeats the base_id filter meaning rather than adding new parameter-level detail, though the detailed materials terminology applies to the response object, not to the input parameters.

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 opens with the specific verb-resource pair 'Check the status of your ship commissions,' which clearly identifies what the tool does. It is easily distinguished from related siblings like commission_ship, supply_commission, and cancel_commission because it focuses on observing active orders, not creating, supplying, or canceling them.

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?

The description makes the primary use case clear: checking active commission status, with an optional base_id filter. It does not explicitly name alternatives or state when not to use this tool, but the context of status checking is unambiguous across a large sibling list.

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

All SpaceMolt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools are clearly distinct, targeting specific actions and resources. A few overlaps exist (e.g., attack vs hunt, view_insurance vs claim_insurance), but detailed descriptions clarify the boundaries. The scale makes selection harder, but each tool has a clear purpose.

Naming Consistency4/5

The majority use a consistent verb_noun snake_case pattern (e.g., create_buy_order, get_cargo, accept_mission). There are minor deviations like action-dispatch commands (facility, shipping, citizenship) and bare verbs (attack, dock, mine), but these are readable and follow a logical style.

Tool Count1/5

With 212 tools, the server far exceeds any reasonable scope for an MCP. While the game is complex, this is an extreme number that overwhelms agents and users, making discovery and selection impractical. The calibration considers 25+ already too many, and 212 is extreme.

Completeness5/5

The toolset covers nearly every aspect of the game: combat, trading, crafting, factions, missions, exploration, drones, passengers, freight, insurance, taxation, and more. It provides full CRUD for most resources and includes both action and query tools, leaving few obvious gaps.

Resources