Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

loot_wreck

Loot items and modules from a wreck (If wreck_id is omitted while towing a wreck, defaults to your towed wreck. Omit item_id and module_id to loot everything that fits: all cargo items and all modules go into your cargo hold. To loot a specific cargo item: include item_id and optional quantity. To fit a specific module directly onto your ship, include module_id — the module type must not be withdrawn, and the ship needs a free slot plus sufficient CPU/power. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idNoSpecific cargo item ID to loot. Omit to loot everything (all cargo and modules go to cargo hold).
quantityNoQuantity of cargo item to loot (only used with item_id)
wreck_idNoUUID of the wreck to loot. Omit when towing a wreck to default to your towed wreck.
module_idNoModule instance ID to loot directly onto your ship (requires free slot, CPU, and power). Get module IDs from get_wrecks. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).
session_idYesYour session ID from login/register

Schema Changelog

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

  1. Changed5 schema fields changed
    • changedInput schema / properties / item_id / description
      Previous value: -"ID of the item or module to loot"New value: +"Specific cargo item ID to loot. Omit to loot everything (all cargo and modules go to cargo hold)."
    • addedInput schema / properties / module_id
      Added value: +{
+  "description": "Module instance ID to loot directly onto your ship (requires free slot, CPU, and power). Get module IDs from get_wrecks. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).",
+  "type": "string"
+}
    • changedInput schema / properties / quantity / description
      Previous value: -"Quantity to loot (use 1 for modules)"New value: +"Quantity of cargo item to loot (only used with item_id)"
    • changedInput schema / properties / wreck_id / description
      Previous value: -"UUID of the wreck to loot"New value: +"UUID of the wreck to loot. Omit when towing a wreck to default to your towed wreck."
    • changedInput schema / required
      Previous value: -[
-  "session_id",
-  "wreck_id",
-  "item_id",
-  "quantity"
-]New value: +[
+  "session_id"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With only readOnlyHint=false in annotations, the description carries the full burden and does so well. It discloses the towed-wreck default, the all-loot fallback, direct module fitting behavior, and the Engineering skill bonus affecting CPU/power display. There is no contradiction with the annotations.

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 description is front-loaded with its purpose and every clause earns its place. However, the single long parenthetical with nested conditionals is dense and harder to parse than a bulleted structure would be. There is no filler, but scannability suffers slightly.

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?

All valid invocation modes are covered: default toward towed wreck, all-items loot, specific cargo item loot, and direct module fitting with prerequisites. Since there is no output schema, return values need not be described. The only minor omission is the explicit invalid case of omitting wreck_id while not towing, but this does not prevent correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though the schema already documents each parameter, the description adds critical cross-parameter meaning: quantity is optional and only relevant with item_id, wreck_id defaults to the towed wreck, and module_id changes the operation from cargo loot to direct fit. This is exactly the kind of semantic context the schema alone cannot express.

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 a specific verb and resource ('Loot items and modules from a wreck') and immediately defines three distinct modes: default towed wreck, loot everything, loot specific cargo item, and fit a module directly. This clearly sets it apart from sibling tools like scrap_wreck or sell_wreck even without naming them.

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 parameter-combination guidance: omit item_id and module_id to loot everything, include item_id for a specific cargo item, include module_id to fit a module directly, and omit wreck_id when towing. It also states the module-fitting prerequisites (free slot, CPU/power, module not withdrawn), leaving little to inference.

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