Skip to main content
Glama

SPACE-CORE

by at.space-core
OverviewDiscussionsAdmin

Sell goods

sell
Destructive

Sell ONE item type from your cargo instantly at the station price. Ship must be DOCKED (use dock first) -- being in a sector with a station is not enough. To sell everything use sell_all; to wait for a better price use place_orders (type SELL).

Input Schema

NameRequiredDescriptionDefault
forceNoAlias of ignore_mission_reserve.
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
quantityYesHow many units to sell (integer >= 1, at most what you carry)
item_codeYesItem code of a cargo item, e.g. RAW_TITANIUM (see get_inventory)
ignore_mission_reserveNoSet true (or 1) to sell goods that an active mission still needs too. Without it, only the free amount is sold and a warning names the reserved amount (mission progress may drop). force=true works as an alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / force / description
      Previous value: -"Set true (or 1) to sell goods that an active mission still needs too. Without it, only the free amount is sold and a warning names the reserved amount (mission progress may drop with force)."New value: +"Alias of ignore_mission_reserve."
    • addedInput schema / properties / ignore_mission_reserve
      Added value: +{
+  "description": "Set true (or 1) to sell goods that an active mission still needs too. Without it, only the free amount is sold and a warning names the reserved amount (mission progress may drop). force=true works as an alias.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Set true (or 1) to sell goods that an active mission still needs too. Without it, only the free amount is sold and a warning names the reserved amount (mission progress may drop with force).",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / item_code / description
      Previous value: -"Item code, e.g. RAW_TITANIUM"New value: +"Item code of a cargo item, e.g. RAW_TITANIUM (see get_inventory)"
    • changedInput schema / properties / quantity / description
      Previous value: -"How many to sell"New value: +"How many units to sell (integer >= 1, at most what you carry)"
  4. Changed1 schema field changed
    • addedInput schema / properties / bearer / description
      Added value: +"Your SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header."
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent, so the safety profile is covered. The description adds behavioral context annotations cannot express: the sale is immediate at station price and requires an explicit docking state. It does not mention the mission-reserve side effect or what the response contains, but the docking precondition and execution semantics make this above baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action, then the precondition, then the alternatives. No repetition of the title or filler.

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?

Covers action, scope, precondition, and sibling routing for a destructive trade tool with no output schema. The only gap is that it does not describe what a successful sale returns (units sold, credits received) or partial-failure behavior, which an agent may need to confirm results.

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?

Schema coverage is 100%, so quantity, item_code, force, bearer and ignore_mission_reserve are all fully documented in the schema, including the mission-reserve warning and the force alias. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Sell'), a precise scope ('ONE item type from your cargo'), and the execution model ('instantly at the station price'). The emphasis on ONE item type immediately separates it from sell_all and place_orders, so an agent can pick correctly without opening the schema.

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?

Names both alternatives with the condition selecting each: sell_all for everything, place_orders (type SELL) to wait for a better price. Also states the hard precondition 'Ship must be DOCKED (use dock first) -- being in a sector with a station is not enough,' pre-empting the most likely failure mode.

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

All SPACE-CORE toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources