Skip to main content
Glama
CoinRithm

CoinRithm/coinrithm-agent-trading

Official

Cancel spot order

cancel_spot_order
Destructive

Cancel an open spot order by ID to release frozen funds. Designed for paper trading with virtual funds.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesOpen order id.
agentTraceNoOptional private trace metadata stored in the caller's ledger.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
httpStatusYesHTTP status returned by CoinRithm, or 0 for network errors.
okYesTrue when CoinRithm returned a successful 2xx response.
ledgerEventIdNoPrivate AgentActionEvent id returned by /api/agent/*, when present.
ledgerStatusNoLedger write status header returned by CoinRithm, when present.
bodyNoParsed CoinRithm response body, or raw text when the response is not JSON.
Behavior5/5

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

Description adds behavioral context beyond annotations: 'releases frozen funds' implies a side effect, and 'paper trading only' clarifies environment. Annotations already indicate destructive and open-world, but description enriches understanding without contradiction.

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 concise sentences, front-loaded with the core action, then usage requirements and disclaimer. No wasted words.

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?

Given the tool's simplicity (2 params, output schema exists), the description covers purpose, usage, behavior, and parameters (via schema). It is complete for an agent to use correctly.

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 description coverage is 100% with clear parameter descriptions. The tool description does not add extra meaning beyond what's in the schema, so baseline 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?

Description clearly states the verb 'cancel', the resource 'spot order', and the scope 'by id'. It also adds context 'releases frozen funds'. This distinguishes it from sibling tools like 'place_spot_order' or 'list_open_orders'.

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?

Description specifies required scope 'trade:spot' and that it's paper trading only with virtual funds. It also includes a disclaimer. While it doesn't explicitly state when not to use or list alternatives, the context is sufficient for an agent to decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CoinRithm/coinrithm-agent-trading'

If you have feedback or need assistance with the MCP directory API, please join our Discord server