Skip to main content
Glama

SpaceMolt

by io.github.statico-alt
OverviewDiscussionsAdmin

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 loot a specific module into your cargo hold, include module_id; fit it later at a station with install_mod.)

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 into your cargo hold. Get module IDs from get_wrecks; fit it later at a station with install_mod.
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedInput schema / properties / module_id / description
      Previous value: -"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)."New value: +"Module instance ID to loot into your cargo hold. Get module IDs from get_wrecks; fit it later at a station with install_mod."
  4. 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"
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotation only provides readOnlyHint=false, so the description carries the burden of explaining behavior. It discloses key behaviors: defaulting to the towed wreck, looting 'everything that fits' all at once, routing items to the cargo hold, and deferring module fitting to install_mod. It does not specify what happens to the wreck or how capacity overflows are handled, but it adds meaningful behavioral detail.

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 a single dense paragraph with the main action front-loaded and supporting modes organized in a parenthetical. Every clause adds operational information, though the string is slightly long and could be split into bullets for readability.

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 tool with five parameters, all documented in the schema, and no output schema, the description covers the essential decision logic for looting everything, specific items, or specific modules. It uses install_mod to point at the next step and is sufficient for an agent to invoke correctly, though it omits edge cases such as what happens when the cargo hold cannot fit all loot.

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. The description adds valuable combined semantics beyond individual schema comments: omitting both item_id and module_id means loot everything, wreck_id defaults to the towed wreck, and module_id leads to later fitting via install_mod. This clarifies how the optional parameters interact.

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.' This clearly distinguishes it from sibling tools like scrap_wreck, sell_wreck, tow_wreck, and get_wrecks, which have different actions or intents.

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 explains the main usage modes: defaulting to a towed wreck when wreck_id is omitted, looting everything by omitting both item_id and module_id, looting a specific cargo item with quantity, and looting a specific module. It does not explicitly name alternative tools or state when not to use it, but the contexts are clear.

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