Skip to main content
Glama

SPACE-CORE

by at.space-core
OverviewDiscussionsAdmin

Sell all cargo

sell_all
Destructive

Sell every item in your cargo instantly at the station price. Ship must be DOCKED (use dock first). Material needed for your next ship upgrade is kept on board unless ignore_upgrade_reserve is set; goods an active mission still needs are kept unless ignore_mission_reserve is set. For a single item use sell. Returns the items sold and the CWM received. Irreversible.

Input Schema

NameRequiredDescriptionDefault
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
ignore_mission_reserveNoSet true (or 1) to sell goods that an active mission still needs too instead of keeping them on board. Without it, mission cargo stays in the hold and sell_all answers Nothing sold.
ignore_upgrade_reserveNoSet true (or 1) to sell upgrade material too instead of keeping it on board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ignore_mission_reserve
      Added value: +{
+  "description": "Set true (or 1) to sell goods that an active mission still needs too instead of keeping them on board. Without it, mission cargo stays in the hold and sell_all answers Nothing sold.",
+  "type": "boolean"
+}
    • changedInput schema / properties / ignore_upgrade_reserve / description
      Previous value: -"Sell upgrade material too instead of keeping it on board."New value: +"Set true (or 1) to sell upgrade material too instead of keeping it on board."
  2. 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."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the reservation semantics that determine whether anything sells at all, the prerequisite docking state, the pricing basis, and the explicit warning 'Irreversible.' It also compensates for the missing output schema by stating what comes back (items sold and CWM received).

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?

Four sentences, front-loaded with the action and the blocking prerequisite, then the reserve caveats, then the sibling pointer, then the return/irreversibility note. No filler and each sentence carries a distinct operational fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter mutation tool with no output schema, the description covers prerequisite state, collateral effects (reserved cargo), return content, and irreversibility. Nothing an agent needs in order to invoke it safely is missing.

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% and both optional flags are already fully documented in the schema, including the 'Nothing sold' consequence. The description's sentence about upgrade and mission reserves restates the same defaults rather than adding new semantics, so it does not exceed the baseline for fully covered parameters.

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 and resource ('Sell every item in your cargo') plus the pricing model ('instantly at the station price') and explicitly separates itself from the single-item sibling 'sell'. An agent can distinguish it from 'sell' without opening either 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?

Gives a hard prerequisite ('Ship must be DOCKED (use dock first)'), names the alternative for the narrow case ('For a single item use sell'), and explains the two opt-in flags that change what actually gets sold. When-to-use and when-not-to-use are both covered with named siblings.

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