Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

withdraw_items

Move items from station storage into cargo (or use source/target for direct transfers) (By default items go from your personal storage into cargo. The optional 'source' and 'target' params are forwarded to the unified storage handler — note that to move items between storage areas without going through cargo you should use deposit_items with the appropriate source override (the withdraw verb is only for landing items into cargo). Must have cargo space. Must be docked at a base with storage service.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoOptional. Where the items come from. 'cargo' (default) pulls from your ship's cargo hold. 'storage' pulls from personal station storage (use with target="faction" to bypass cargo). 'faction' pulls from faction storage (use with deposit + target="self" to move directly into personal storage; requires manage_treasury).
targetNoOptional. Destination for the items. 'self' (default) is your personal station storage. 'faction' is your faction's shared storage. 'faction:TAG' donates to another faction. A player name gifts to that player. Combine with source to skip cargo entirely (e.g. source=storage, target=faction).
item_idYesID of the item (e.g., iron_ore, fuel_cell)
quantityYesQuantity to deposit or withdraw
session_idYesYour session ID from login/register

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Optional. Where the items come from. 'cargo' (default) pulls from your ship's cargo hold. 'storage' pulls from personal station storage (use with target=\"faction\" to bypass cargo). 'faction' pulls from faction storage (use with deposit + target=\"self\" to move directly into personal storage; requires manage_treasury).",
+  "enum": [
+    "cargo",
+    "storage",
+    "faction"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "description": "Optional. Destination for the items. 'self' (default) is your personal station storage. 'faction' is your faction's shared storage. 'faction:TAG' donates to another faction. A player name gifts to that player. Combine with source to skip cargo entirely (e.g. source=storage, target=faction).",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / item_id / description
      Previous value: -"ID of the item (e.g., ore_iron, fuel_cell)"New value: +"ID of the item (e.g., iron_ore, fuel_cell)"
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations only include readOnlyHint: false, so the description carries the burden of behavioral disclosure. It reveals that the operation moves items, requires cargo space and docking, and explains that source/target parameters are forwarded to the unified storage handler. It also clarifies the default behavior (personal storage to cargo) and the limitation that the withdraw verb is 'only for landing items into cargo.' No contradiction with 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 a single, rather dense sentence in parentheses, but it packs key details without redundancy. It is not overly long, though the structure could be improved by splitting into separate sentences for readability. Still, every sentence earns its place.

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?

Given the tool's complexity (5 params, no output schema), the description covers the important constraints: cargo space, docking requirement, default behavior, and the alternative tool. It does not describe the return value, but for a transfer operation this is arguably not essential. Overall it gives sufficient context to safely invoke the tool.

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% with detailed parameter descriptions, so the baseline is 3. The description adds extra meaning though: it explains that source/target are forwarded to the unified storage handler and gives the default flow, which complements the schema's per-parameter details. This goes beyond simply repeating schema information.

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 action: 'Move items from station storage into cargo' and identifies the resource (station storage/cargo). It also distinguishes itself from deposit_items by explicitly mentioning that storage-to-storage transfers should use deposit_items instead, making its purpose unambiguous.

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 provides explicit when-to-use guidance: when moving items from storage to cargo, and gives a clear alternative ('deposit_items with the appropriate source override') for when not to use it. It also states prerequisites: 'Must have cargo space' and 'Must be docked at a base with storage service.'

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