Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Cancel an order

cancel_order
Destructive

Cancels an open or partially filled order by ID and releases the reserved balance or shares; only the unfilled remainder is removed.

Instructions

Cancels one of the user's open or partially filled orders by id, releasing the balance or shares it reserved. Shares that already filled stay filled; only the unfilled remainder is cancelled. Orders that are filled, already cancelled or still processing cannot be cancelled, so check the status with list_orders first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order_id": "<order_id>"
    },
    "name": "cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesId of the order to cancel, from list_orders or place_bet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations' destructiveHint/not-idempotent flags, it explains the actual side effects: the reserved balance or shares are released, and partially filled orders only lose the unfilled remainder. That partial-fill semantics detail is exactly the kind of behavior an agent cannot infer from annotations and would otherwise guess wrong.

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 short sentences, front-loaded with the action and outcome, then partial-fill caveat, then failure conditions. No filler and no repetition of the title.

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?

For a single-parameter destructive mutation with no output schema, the description covers side effects, partial-fill behavior and refusal conditions thoroughly. The only gap is that it never hints at what the call returns (e.g. a cancelled order object or confirmation), leaving the response shape entirely unspecified.

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?

With one parameter and 100% schema description coverage, the schema already documents order_id and its provenance ("from list_orders or place_bet"). The description's "by id" restates rather than extends that, so 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?

The description states a specific verb and resource ("Cancels ... orders") plus the exact scope ("open or partially filled ... by id"), which makes it trivially distinguishable from cancel_all_orders. An agent knows precisely what single-order effect to expect before reading 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit preconditions ("check the status with list_orders first") and enumerates the states that block cancellation (filled, already cancelled, still processing). It does not mention cancel_all_orders as the bulk alternative, which is the one obvious sibling routing decision left implicit.

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