Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

faction_deposit_items

Move items from your cargo (or directly from personal storage) into faction storage (Any faction member can deposit items. Set source="storage" to move items directly from your personal station storage into faction storage in a single call (no cargo loop). All deposits 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.3/5.0
Behavior4/5

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

Beyond the annotation (readOnlyHint: false), the description discloses that deposits are tracked in the audit log, that any faction member can deposit, and that using source='storage' avoids a cargo loop. These are behavioral details not available in the annotation or schema, adding meaningful transparency.

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 the main action and then provides relevant details. Though the parenthetical contains multiple sentences and is slightly clunky, every piece of information (permissions, source shortcut, audit log) is useful and earns its place. It is appropriately sized for the tool's complexity.

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 mutation annotations, the description covers the essential context: what the tool does, the alternative source path, permissions, and audit logging. While it does not explain return values, it is reasonably complete for a deposit action, especially with full schema coverage.

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 baseline is 3. The description adds value by explaining the purpose and effect of the 'storage' source value ('move items directly from your personal station storage into faction storage in a single call (no cargo loop)'), which goes beyond the schema's literal definition. It also clarifies the permission context for deposits.

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 your cargo (or directly from personal storage) into faction storage.' It uses a specific verb ('Move') and resource ('faction storage'), and distinguishes from siblings like deposit_items by specifying faction storage and noting 'Any faction member can deposit items.'

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 provides clear context for when to use the tool (depositing into faction storage) and includes a specific usage tip: 'Set source="storage" to move items directly from your personal station storage into faction storage in a single call (no cargo loop).' It does not explicitly mention when not to use it or alternatives, but the guidance is useful and 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
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