Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

batch_cancel_order

Cancel up to 10 orders in one request. Specify category and list of orders with symbol and order ID to efficiently manage your trades.

Instructions

Cancel multiple orders in a single request (max 10).

Args: category: Product type: spot, linear, inverse, option. orders: List of order dicts. Each must contain: symbol and orderId (or orderLinkId). Example: [{"symbol": "BTCUSDT", "orderId": "123456"}]

Returns: Batch cancellation results.

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": {
      "category": "<category>",
      "orders": "<orders>"
    },
    "name": "batch_cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes
ordersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided. Description states it cancels orders (mutation) and imposes a 10-order limit. Does not cover idempotency, partial failures, or auth requirements. Adequate for a simple batch operation.

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?

Concise three-sentence description with clear sections (Args, Returns). No superfluous content. Well-structured and easy to parse.

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?

Covers essential parameter details and return value placeholder. Lacks specification of result structure (e.g., per-order status). Adequate for a straightforward batch cancel tool.

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

Parameters5/5

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

Schema has 0% description coverage. Description fully explains 'category' values (spot, linear, inverse, option) and 'orders' structure (list of dicts with symbol and orderId/orderLinkId). Provides an example. Adds significant meaning beyond schema.

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 'Cancel multiple orders in a single request (max 10).' The verb 'cancel' and resource 'multiple orders' are specific. It distinguishes from siblings like 'cancel_order' (single) and 'cancel_all_orders' (all).

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?

Explicitly mentions 'max 10' indicating when to use (up to 10 orders) and when not (more than 10). However, does not explicitly contrast with alternatives like cancel_all_orders for mass cancellation.

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