Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

cancel_order

Destructive

Cancel an existing order on Bybit. Specify the category and symbol, along with either the order ID or custom link ID.

Instructions

Cancel an existing order (MEDIUM risk - no confirmation required).

    Args:
        category: Product type - spot, linear, inverse, option
        symbol: Symbol name
        orderId: Order ID (either orderId or orderLinkId required)
        orderLinkId: User custom order ID
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
orderIdNo
categoryYes
orderLinkIdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Adds 'MEDIUM risk - no confirmation required' which provides behavioral context beyond the destructiveHint annotation. However, does not describe side effects or failure modes.

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 with one sentence plus bulleted parameter explanations. No superfluous text, all information is relevant and front-loaded.

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?

Good coverage of purpose, risk, and parameters. Lacks mention of failure conditions or confirmation of cancellation. Output schema presence reduces need for return value description.

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?

Despite 0% schema description coverage, the description explains each parameter (category types, symbol name, order ID options) which adds meaning beyond the raw 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 an existing order' with specific verb and resource. Mentions risk level and distinguishes from siblings like cancel_all_orders.

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?

No explicit when-to-use or when-not-to-use guidance. Implies cancellation of active orders but does not specify prerequisites or scenarios where it should be avoided.

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/workspace/bybit-mcp-server'

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