Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cancel_withdrawal

Cancel a pending withdrawal by specifying its ID. Stops the withdrawal from being processed.

Instructions

Cancel a pending withdrawal.

Args: withdraw_id: Withdrawal ID.

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": {
      "withdraw_id": "<withdraw_id>"
    },
    "name": "cancel_withdrawal"
  }
}

Input Schema

NameRequiredDescriptionDefault
withdraw_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description must fully disclose behaviors. It only implies a state change without detailing side effects, such as whether funds are returned, fees apply, or if the operation is idempotent.

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?

The description is very concise with two short sentences, front-loading the main action. The structured 'Args' section is efficient, though the lack of additional context is a minor drawback.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description covers the basic function but omits context about what constitutes a 'pending' withdrawal and any limitations. It is minimally complete.

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?

The schema has 0% description coverage, but the description explains that 'withdraw_id' is the 'Withdrawal ID.' This adds some meaning beyond the schema's title, though it is minimal and does not specify the format or source of the ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Cancel' and the resource 'pending withdrawal', making the tool's purpose immediately understandable. However, it could be more specific by defining what 'pending' means in this context.

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?

No guidance is provided on when to use this tool versus alternative cancel tools (e.g., cancel_order, cancel_rfq). There is no mention of prerequisites or conditions under which a withdrawal can be cancelled.

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