Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Cancel all open orders

cancel_all_orders
Destructive

Cancels every open Futuur order on the account, or only orders for a selected event or market; mid-fill orders are skipped and returned for retry.

Instructions

Cancels every open order of the user, optionally only those on one event or one market. Orders caught mid-fill are skipped and returned in processing_order_ids; try those again shortly with cancel_order. To cancel everything on the account, pass cancel_everything: true and no event or market; only do that when the user asked for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_all_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNoOnly cancel orders on this event id.
marketNoOnly cancel orders on this market (outcome) id.
cancel_everythingNoMust be true when neither `event` nor `market` is given, to confirm that every open order on the account should be cancelled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description still adds real behavioral value the annotations cannot: orders caught mid-fill are skipped and surfaced in `processing_order_ids`, which tells the agent the operation can partially succeed and how to recover. It stops short of describing full pagination or total-count reporting, so not a 5.

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 tight sentences: what it does, what happens on partial failure plus the fix, then the dangerous-flag condition. The destructive guidance is placed last and clearly marked, which suits a cancel-everything tool.

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 destructive bulk operation with no output schema, the definition covers scope, partial-failure semantics, the recovery path, and the confirmation requirement for the account-wide case. An agent has everything needed to decide whether to call it and how to handle the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by explaining the coupling between the parameters (cancel_everything must accompany an empty event/market) as a safety confirmation rather than a plain flag. It also adds the caution to use that flag only on explicit user request, which the schema description does not convey.

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 opens with a specific verb and resource ('Cancels every open order of the user') and immediately scopes it ('optionally only those on one event or one market'). That scope distinction separates it cleanly from the singular cancel_order sibling without needing to inspect 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?

It gives explicit routing: retry mid-fill orders shortly with cancel_order, and use cancel_everything: true with no event/market only 'when the user asked for it.' That is a when-to-use, a when-not-to-use, and a named alternative in two sentences.

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