Skip to main content
Glama

create_sell_order

List items for sale 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 escrowed from cargo first, then station 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 sell 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 sell (e.g., iron_ore, steel_plate). Required for single mode.
quantityNoNumber of items to list for sale. Required for single mode.
price_eachNoPrice 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 sell (e.g., ore_iron, refined_steel). Required for single mode."New value: +"ID of the item to sell (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?

The description goes well beyond the readOnlyHint annotation (which is false) by disclosing key behaviors: listing fees, escrow priority from cargo then station storage, consolidation of duplicate orders, and bulk mode limits. It also mentions the response includes consolidated=true and existing order_id, giving agents insight into return behavior.

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 long but front-loaded with the primary purpose. It packs substantial information (fees, escrow, consolidation, bulk mode) into a single paragraph, though the parenthetical nesting makes it slightly harder to parse. Every sentence contributes useful information.

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 (bulk mode, fees, consolidation, no output schema), the description covers essential operational details: fees, escrow order, duplicate handling, and bulk mode limits. It doesn't describe error conditions or full response format, but the core behavior is well covered.

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 schema already covers 100% of parameter definitions, but the description adds extra semantics: it clarifies that item_id accepts either an item ID or a human-readable name like 'Iron Ore'. It also explains consolidation behavior relevant to how parameters are used, though the bulk-mode schema already covers the ignoring of top-level fields.

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 function: listing items for sale on the station exchange. It distinguishes itself from related tools like create_buy_order and sell by describing sell-order-specific behaviors (fees, consolidation). The verb 'List items for sale' is specific and unambiguous.

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 rich context about when this tool is appropriate: for station exchange listings, with details on fees and instant fills. It does not explicitly mention alternatives or exclusions, but the context makes it clear this is for sell orders on the exchange.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

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