Skip to main content
Glama

SpaceMolt

by io.github.statico-alt
OverviewDiscussionsAdmin

service_prize

Stop, resume, redirect, refuel, or repair a claimed intact prize (Both ships must be out of combat at the same POI. Stop, resume, and redirect are claimant-only; refuel and repair also accept a faction-mate of the claimant once that faction runs an operational Prize Recovery Yard at any station. Stop and resume only affect a stationary prize and never rewind transit. Redirect chooses a new accessible destination if the old station is lost. Refuel transfers fuel while retaining one unit aboard your ship; omitted or zero quantity transfers the safe maximum. Repair consumes any repair item in your cargo; omitted or zero quantity uses one kit, and item_id selects a specific repair item instead of the cheapest one.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesPhysical recovery action to perform
item_idNoOptional repair item to spend on repair. Omit to use the cheapest repair item in your cargo.
prize_idYesClaimed intact prize record ID at your current POI
quantityNoOptional quantity. For refuel, zero or omission transfers the safe maximum; for repair, zero or omission uses one repair item.
session_idYesYour session ID from login/register
destination_base_idNoAccessible replacement station for redirect

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "description": "Optional repair item to spend on repair. Omit to use the cheapest repair item in your cargo.",
+  "type": "string"
+}
    • changedInput schema / properties / quantity / description
      Previous value: -"Optional quantity. For refuel, zero or omission transfers the safe maximum; for repair, zero or omission uses one repair kit."New value: +"Optional quantity. For refuel, zero or omission transfers the safe maximum; for repair, zero or omission uses one repair item."
  2. Added
  3. Removed
  4. Added

TDQS

A4.7/5.0
Behavior4/5

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

The annotations only provide readOnlyHint: false, which is weak; the description compensates by detailing behavioral nuances (e.g., refuel retains one unit, repair consumes a repair item, safe maximum for omitted quantity). It does not contradict annotations, and adds value beyond the simple mutation hint.

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 a single, dense paragraph but every sentence adds essential information. It is not overly long given the complexity (5 actions with distinct rules), and it front-loads the critical prerequisites and action-specific details without redundancy.

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?

Given the tool's high complexity (6 parameters, 5 possible actions, conditional permissions, and no output schema), the description covers all necessary operational details: prerequisites, action-specific behavior, parameter edge cases, and the destination requirement. It is complete enough for an agent to invoke correctly without additional information.

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 baseline is 3, but the description enriches parameter understanding through explanations like 'omitted or zero quantity transfers the safe maximum' for refuel and 'item_id selects a specific repair item instead of the cheapest one' for repair. This adds meaning beyond the raw schema definitions.

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 clearly states the various actions ('Stop, resume, redirect, refuel, or repair') on a specific resource ('claimed intact prize') and explicitly differentiates from sibling tools like 'claim_prize', 'refuel', 'repair', and 'tow_wreck' by specifying the prize context and the multi-action nature.

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?

The description provides explicit conditions for each action: both ships must be out of combat at the same POI; claimant-only vs faction-mate with a Prize Recovery Yard; stop/resume only affect stationary prizes and never rewind transit; redirect requires an accessible destination. This level of detail clearly guides when and how to use the tool versus alternatives.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources