Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

faction_withdraw_items

Move items from faction storage to your cargo (or use source/target for direct transfers) (Requires manage_treasury permission. Default destination is cargo (must have cargo space). The optional 'source' and 'target' params are forwarded to the unified storage handler — to move items from faction storage directly into your personal storage in one call, prefer deposit_items with source="faction" and target="self". All withdrawals are tracked in the audit log.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoOptional. Where the items come from. Defaults to 'cargo'. Set to 'storage' on faction_deposit_items to move directly from personal storage into faction storage without going through cargo.
targetNoOptional. Destination for the items. Defaults to 'faction' (your faction's storage). Override only when you need a different routing — see the spacemolt_storage tool docs for advanced patterns.
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. Defaults to 'cargo'. Set to 'storage' on faction_deposit_items to move directly from personal storage into faction storage without going through cargo.",
+  "enum": [
+    "cargo",
+    "storage",
+    "faction"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "description": "Optional. Destination for the items. Defaults to 'faction' (your faction's storage). Override only when you need a different routing — see the spacemolt_storage tool docs for advanced patterns.",
+  "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
Behavior5/5

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

Annotations only provide readOnlyHint: false, so the description carries the burden of behavioral context. It discloses the required 'manage_treasury' permission, the cargo space requirement, that withdrawals are tracked in the audit log, and that source/target params are forwarded to the unified storage handler. This goes well beyond the annotation.

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 dense and contains all necessary information, but it is structured with nested parentheticals that make parsing slightly harder. It is not overly long and each sentence adds value, but the awkward phrasing and parenthetical stacking cost a point.

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 has 5 parameters, no output schema, and minimal annotations, the description covers the essential aspects: action, permission, defaults, audit logging, and an alternative tool. It does not explain return values or error conditions, but those are not required due to the absence of an output schema. The contradiction with the target default prevents a perfect score.

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

Parameters3/5

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

While schema coverage is 100%, the description adds meaning about routing through the unified storage handler and clarifies defaults. However, there is a contradiction: the description says 'Default destination is cargo', but the schema for target states 'Defaults to faction'. This conflicting information reduces clarity and could mislead an agent despite the description offering additional context.

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 tool's action: 'Move items from faction storage to your cargo', with a specific verb and resource, and distinguishes it from related tools by mentioning source/target for direct transfers and pointing to deposit_items as an alternative. This differentiates it from siblings like faction_deposit_items and withdraw_items.

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 explicitly provides usage guidance by stating that for moving items from faction storage directly into personal storage in one call, one should 'prefer deposit_items with source="faction" and target="self"' instead. It also notes the default destination is cargo and requires cargo space, giving clear context on when to use this tool.

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