Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

sell

Sell items at market price on the station exchange (No fees for instant fills. Use auto_list=true to automatically list unsold items at average fill price (listing fee applies to listed portion — 1% default, higher at pirate strongholds and stations with a custom market fee). Accepts item_id or item name (e.g. 'Iron Ore').)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesID of the item to sell (e.g., iron_ore, steel_plate)
quantityYesQuantity to sell
auto_listNoIf true, automatically create a sell order for unsold items at the average fill price (1% listing fee applies).
session_idYesYour session ID from login/register

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / item_id / description
      Previous value: -"ID of the item to sell (e.g., ore_iron, refined_steel)"New value: +"ID of the item to sell (e.g., iron_ore, steel_plate)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the readOnlyHint=false annotation: it details the fee structure (no fees for instant fills, 1% listing fee on auto-listed portions, with variations), and explains the auto_list fallback mechanism. It does not cover all effects (e.g., response format), but the disclosed details are valuable.

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, front-loaded sentence beginning with the core purpose. It includes several parentheticals and clauses that make it somewhat dense, but every part contributes useful information, so it remains appropriately concise and structured.

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 sell tool with 4 parameters and no output schema, the description covers the essential context: purpose, pricing, auto-list behavior, and input format flexibility. It lacks details on return values, partial fills, or error conditions, but given the tool's simplicity, it is reasonably complete.

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?

While the schema already documents all parameters (coverage 100%), the description enriches understanding by stating that item_id accepts both IDs and item names (e.g., 'Iron Ore'), and clarifies auto_list's behavior beyond the schema's brief description. This adds real value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: selling items at market price on the station exchange with instant fills. It distinguishes itself from order-based tools like create_sell_order through the focus on immediate execution, though it does not explicitly name any siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the mention of instant fills and the auto_list parameter, but no explicit guidance is given on when to use this tool versus alternatives like create_sell_order or buy. The conditional for auto_list provides some direction, but the description lacks exclusions or comparisons.

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