Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

cancel_all_orders

Cancel all open trading orders through the Interactive Brokers API. This tool removes pending trade requests to manage positions and prevent unwanted executions.

Instructions

Cancel all open orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the cancel_all_orders tool, which calls ib.reqGlobalCancel().
    if name == "cancel_all_orders":
        ib.reqGlobalCancel()
        return {"status": "cancel_all_requested"}
  • The registration of the cancel_all_orders tool with its description and schema.
    Tool(
        name="cancel_all_orders",
        description="Cancel all open orders.",
        inputSchema={"type": "object", "properties": {}},
    ),
Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. While 'cancel' implies mutation, there is no mention of irreversibility, handling of partially filled orders, error behavior if no orders exist, or success indicators—critical omissions for a destructive bulk operation.

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

Conciseness4/5

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

Extremely brief at four words with no redundancy. However, given the high-stakes destructive nature of the operation, this brevity borders on under-specification rather than efficient communication.

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

Completeness2/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 and no annotations, the description is dangerously minimal. It lacks safety warnings, scope clarification (all accounts vs. specific), and behavioral expectations that would prevent accidental misuse.

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?

Input schema has zero parameters, establishing baseline 4. The description requires no parameter explanation.

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 'Cancel all open orders' provides a specific verb (cancel), clear resource (orders), and scope modifier (all/open) that effectively distinguishes it from sibling tool 'cancel_order' (singular).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no explicit guidance on when to use this versus the singular 'cancel_order', nor warnings about the bulk irreversible nature of the operation. The 'all' implies scope but doesn't guide decision-making.

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/nadavgb-atom/ib-async-mcp'

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