CoinRithm Agent Trading

Cancel spot order

cancel_spot_order

Destructive

Cancel an open spot order by id (releases frozen funds). Requires the trade:spot scope. Paper trading only — virtual funds (50,000 mUSD). Not financial advice. Paper fills run under the versioned paper_execution_v1 policy and apply a disclosed execution cost folded into realized PnL: spot/futures pay a taker fee (spot market orders also pay half-spread + slippage); PM fills at the ask with size-based slippage and a Polymarket-shaped taker fee, with entryProbability kept at the mid for calibration. See the executionModel in quote/trade results — a rehearsal cost, not an exchange fill guarantee.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`orderId`	Yes	Open order id.
`agentTrace`	No	Optional private trace metadata stored in the caller's ledger.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when CoinRithm returned a successful 2xx response.
`body`	No	Parsed CoinRithm response body, or raw text when the response is not JSON.
`httpStatus`	Yes	HTTP status returned by CoinRithm, or 0 for network errors.
`ledgerStatus`	No	Ledger write status header returned by CoinRithm, when present.
`ledgerEventId`	No	Private AgentActionEvent id returned by /api/agent/*, when present.

TDQS

A3.8/5.0

Behavior4/5

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

Annotations indicate destructive behavior; the description adds 'releases frozen funds', confirming mutation. The long paragraph on paper execution policy and costs provides additional behavioral context beyond annotations, though some details may be tangential to cancellation.

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

Conciseness2/5

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

The description is verbose and includes an entire paragraph about paper fill execution models, which seems more relevant to placing orders than canceling. This detracts from conciseness and focus.

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

Completeness3/5

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

The description covers the basic purpose, scope, and paper trading context, but includes irrelevant execution policy details while omitting error scenarios (e.g., what if order not found). An output schema exists, so return values are handled. Adequate but not thorough.

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 the description adds no new information beyond the schema. The main description mentions 'by id' but that is already in the parameter schema. Baseline of 3 is appropriate.

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 cancels an open spot order by ID, distinguishing it from siblings like place_spot_order or list_open_orders. The verb 'cancel' and resource 'open spot order by id' are 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 specifies the required scope (trade:spot) and that it is paper trading only, providing clear context. However, it does not explicitly state when to use this tool versus alternatives or discuss exclusions.

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

All CoinRithm Agent Trading tools Inspect

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

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but a few could be confused (e.g., get_performance vs get_equity_curve, get_portfolio vs get_wallet). Descriptions help differentiate them.

Naming Consistency4/5

Predominantly verb_noun (get_*, place_*, open_*, etc.) with a consistent pm_data_* prefix for prediction market data tools. Minor outliers like whoami and futures_quote/spot_quote without a verb are exceptions.

Tool Count4/5

37 tools is slightly high but appropriate for a multi-venue trading platform covering spot, futures, and prediction markets along with extensive data and performance tracking tools.

Completeness4/5

Covers core trading lifecycle (quote, open, close, cancel) for all venues, plus market data, ledger exports, and arena leaderboards. Lacks spot order modification but otherwise well-rounded.

Resources

Need Help?