Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

create_buy_order

Place a buy offer on the station exchange (Listing fee on the portion that goes on the order book (1% default; pirate strongholds and stations with a custom market fee charge more). Instant fills incur no fee. Items from instant fills delivered to cargo by default (use deliver_to=storage for storage). Accepts item_id or item name (e.g. 'Iron Ore'). Bulk mode: pass 'orders' array of {item_id, quantity, price_each} to create up to 50 orders in one call. If you already have an order for the same item at the same price, the new quantity is added to your existing order instead of creating a duplicate (response includes consolidated=true and the existing order_id).)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ordersNoBulk mode: array of buy orders to create (max 50). Each entry needs item_id, quantity, price_each. When provided, the top-level item_id/quantity/price_each are ignored.
item_idNoID of the item to buy (e.g., iron_ore, steel_plate). Required for single mode.
quantityNoNumber of items to buy. Required for single mode.
deliver_toNoWhere to deliver filled items: 'cargo' (default) or 'storage' (station storage).
price_eachNoMaximum price per unit in credits. Required for single mode.
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 buy (e.g., ore_iron, refined_steel). Required for single mode."New value: +"ID of the item to buy (e.g., iron_ore, steel_plate). Required for single mode."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint=false annotation, the description reveals substantial behavioral details: listing fees on order book portions, instant fills incurring no fee, delivery defaulting to cargo, consolidation of matching orders, and bulk mode limits. This significantly enriches the agent's understanding of side effects and edge cases.

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 dense paragraph with useful information. It front-loads the main purpose, then covers fees, delivery, item naming, bulk mode, and consolidation. It is concise but slightly long; breaking into bullets could improve scannability without adding length. Still, every sentence provides value.

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 complexity (bulk mode, fees, consolidation, delivery options) and no output schema, the description covers most important behavior. It explains the consolidation response detail but does not describe the general return payload or error conditions. It is reasonably complete for a create-order operation with rich annotations.

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?

The input schema already covers all 6 parameters with descriptions (100% coverage), so baseline is 3. The description adds meaning by clarifying that item_id accepts item names (e.g., 'Iron Ore'), explaining bulk mode semantics, and specifying default deliver_to behavior. This exceeds schema information but does not fully reinvent parameter documentation.

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 'Place a buy offer on the station exchange', identifying the specific verb and resource. It distinguishes from related tools like 'create_sell_order' and 'buy' by focusing on exchange buy offers, and adds unique details like listing fees and order consolidation.

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 using the tool, including fee structure, delivery options, and bulk mode. It implies when to use it (placing buy orders on the station exchange) but does not explicitly contrast with direct purchase tools like 'buy' or mention when not to use it. This is clear context without explicit exclusions.

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