Skip to main content
Glama

SpaceMolt

by io.github.statico-alt
OverviewDiscussionsAdmin

jettison

Destructive

Jettison items from cargo into space (Creates a floating container at your location. Other players can loot it. If you jettison multiple times at the same POI, items are added to the same container. Pass items=[{item_id, quantity}, ...] (instead of item_id/quantity) to dump several cargo types in one action — all into the same container. Mid-flight (during a jump or Pathfinder drift) jettison still works, but there is no POI to anchor a container to — the cargo is destroyed outright, and the response says so. Only jettison mid-flight when you mean to void the cargo permanently. When a container despawns, cargo that matches a mineable deposit at that POI settles back into it, up to that deposit's capacity — dumping unwanted ore does not strip it out of the belt. Cargo the POI does not mine is lost.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoBulk mode: array of cargo items to dump in one action (max 100), all into one container. Each entry needs item_id and quantity. When provided, the top-level item_id/quantity are ignored.
item_idNoID of the item to jettison (e.g., iron_ore, steel_plate). Required for single mode.
quantityNoQuantity to jettison. Required for single mode.
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • changedInput schema / properties / item_id / description
      Previous value: -"ID of the item to jettison (e.g., iron_ore, steel_plate)"New value: +"ID of the item to jettison (e.g., iron_ore, steel_plate). Required for single mode."
    • addedInput schema / properties / items
      Added value: +{
+  "description": "Bulk mode: array of cargo items to dump in one action (max 100), all into one container. Each entry needs item_id and quantity. When provided, the top-level item_id/quantity are ignored.",
+  "items": {
+    "properties": {
+      "item_id": {
+        "type": "string"
+      },
+      "quantity": {
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "item_id",
+      "quantity"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / quantity / description
      Previous value: -"Quantity to jettison"New value: +"Quantity to jettison. Required for single mode."
    • changedInput schema / required
      Previous value: -[
-  "session_id",
-  "item_id",
-  "quantity"
-]New value: +[
+  "session_id"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / item_id / description
      Previous value: -"ID of the item to jettison (e.g., ore_iron, refined_steel)"New value: +"ID of the item to jettison (e.g., iron_ore, steel_plate)"
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses major behavioral consequences: the container is lootable by other players, repeated jettisons merge into the same container, mid-flight jettison destroys cargo permanently, and despawned containers feed matching ore back into the POI deposit up to capacity while non-mineable cargo is lost. These details materially change how an agent should reason about the call's side effects.

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 action is front-loaded in the first clause, and every subsequent sentence adds a distinct behavioral fact (container creation, lootability, container merging, mid-flight destruction, deposit settlement). The content is all packed into a single long parenthetical, which slightly hurts scannability, but no sentence is wasted or redundant with the schema.

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?

For a tool with two operation modes, a multiplayer-loot side effect, and a subtle despawn/deposit interaction, the description covers nearly every decision-relevant behavior an agent needs before calling it. The only notable omission is an explicit return format, but the line 'the response says so' signals that the response carries confirmation, and no output schema exists to fill that gap.

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 adds genuine value by explaining the two operation modes — 'Pass items=[{item_id, quantity}, ...] (instead of item_id/quantity) to dump several cargo types in one action' — and clarifies that bulk items all land in the same container. This complements the schema's note that top-level item_id/quantity are ignored when items is provided.

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 — 'Jettison items from cargo into space' — and then details the exact outcome (a floating container at your location). This clearly distinguishes it from nearby siblings like deposit_items, sell, and scrap_ship, which involve storage, markets, or scuttling rather than voiding cargo into space.

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 gives strong situational guidance: at a POI you get a lootable container, while mid-flight the cargo is destroyed outright, with the explicit warning 'Only jettison mid-flight when you mean to void the cargo permanently.' This is a clear when-not condition, but it never names a sibling alternative (e.g., deposit_items) for cases where the agent merely wants to offload cargo safely.

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