Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cancel_all_orders

Cancel all open orders for a specified trading pair, supporting spot, linear, and inverse categories.

Instructions

Cancel all open orders for a symbol.

Args: symbol: The trading pair. category: Product type: spot, linear, inverse (default: spot).

Returns: Cancellation result.

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": {
      "symbol": "<symbol>"
    },
    "name": "cancel_all_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
categoryNospot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

The description states the action (cancelling) but, without annotations, fails to disclose important behavioral traits such as whether cancellation is reversible, required permissions, or any rate limits. It lacks context on side effects beyond stating the action.

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?

The description is extremely concise: a single sentence followed by a parameter list. It front-loads the purpose with no unnecessary words, making it efficient for an agent to parse.

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?

Given no output schema and no annotations, the description is incomplete. It lacks details on return value structure, error conditions, or the scope of cancellation (e.g., whether it applies to all categories or only the one specified). The parameter list does not clarify default behavior beyond the schema default.

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 0% schema description coverage, the description adds minimal value beyond the schema. It explains 'category' values ('spot, linear, inverse') but does not elaborate on 'symbol' beyond 'The trading pair.' This improves understanding but does not fully compensate for the lack of schema-level descriptions.

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 for a symbol' uses a specific verb ('Cancel') and resource ('open orders'), clearly distinguishing it from siblings like 'cancel_order' (which cancels a single order) or 'cancel_spread_order'.

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

Usage Guidelines3/5

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

The description implies usage when you want to cancel multiple orders for a symbol but provides no explicit guidance on when to use it versus alternatives (e.g., 'cancel_order' for single orders, 'batch_cancel_order' for specific IDs). No when-not-to-use or preconditions are stated.

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

Deploy Server

Other Tools