SpaceMolt

commission_quote

Read-onlyIdempotent

Get a cost estimate for commissioning a ship (Returns detailed pricing and requirements. Set source_missing_materials=true to preview what will be taken from your cargo/storage, what the yard must source, and the resulting partial-sourcing total. Set bare_hull=true to exclude the default module loadout. Does not place an order.)

Input Schema

TableJSON Schema

Name	Required	Description
`bare_hull`	No	If true, quote the hull without its default module loadout.
`session_id`	Yes	Your session ID from login/register
`ship_class`	Yes	Ship class ID to get a quote for
`source_missing_materials`	No	Preview the materials you can contribute, the remaining deficit, and partial-sourcing total.

Schema Changelog

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

Changed2 schema fields changedAug 29, 2026

addedInput schema / properties / bare_hull

Added value: +{
+  "description": "If true, quote the hull without its default module loadout.",
+  "type": "boolean"
+}

addedInput schema / properties / source_missing_materials

Added value: +{
+  "description": "Preview the materials you can contribute, the remaining deficit, and partial-sourcing total.",
+  "type": "boolean"
+}

First observedFeb 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is known. The description adds behavioral details beyond the flags: it returns pricing and requirements, previews partial-sourcing totals, and explicitly disclaims order placement. This gives the agent confidence the call is non-mutating and explains the effect of each preview mode.

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 packs the core purpose, the two relevant boolean modes, and the critical no-order note into one compact sentence. It is front-loaded with the main action, and every clause carries information with no filler or repetition.

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?

For a read-only quote tool with no output schema, the description provides enough invocation context: purpose, two modifier flags, and the no-order guarantee. It does not detail the exact response fields, but 'detailed pricing and requirements' plus the parameter explanations is adequate for an agent to call it correctly. Both required parameters are clear from the schema.

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 every parameter already has a schema description and the baseline is 3. The description raises this by explaining the behavioral meaning of source_missing_materials and bare_hull in terms of cargo contribution, yard sourcing, and module loadouts. It adds why those booleans matter rather than just their type.

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 names a specific verb and resource ('Get a cost estimate for commissioning a ship') and immediately clarifies the tool's output as detailed pricing and requirements. The closing 'Does not place an order' differentiates it from siblings like commission_ship, so an agent can tell it apart without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly establishes the tool as estimation-only with 'Does not place an order', acting as a when-not signal. It also explains when to set source_missing_materials and bare_hull, giving context for the two conditional modes. It stops short of explicitly naming sibling alternatives like commission_ship or commission_status.

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

All SpaceMolt tools Inspect

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

Need Help?