Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

postCryptoLoanFixedSupplyOrderCancel

Cancel a pending crypto loan fixed supply lending order to unlock funds. Specify the order ID and optionally choose a refund account.

Instructions

Cancel a pending supply (lending) order.

Rate limit: 1 request per UID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYes
refundedAccountNo0
Behavior2/5

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

The only behavioral context is a rate limit of 1 request per UID. No annotations exist. The description does not disclose side effects (e.g., refund behavior, impact on orders) or explain what happens upon cancellation.

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?

Extremely concise: two well-structured sentences. Purpose is front-loaded, rate limit is a helpful addition. No extraneous text.

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?

Lacks crucial context: no output schema, no explanation of refundedAccount, no description of error states or prerequisites. For a cancellation tool, more context is needed for correct invocation.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no explanation for parameters. orderId is obvious, but refundedAccount with enum '0','1' is cryptic and not explained, leaving ambiguity about its meaning.

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 clearly states it cancels a pending supply (lending) order. The verb 'Cancel' and resource 'supply order' are specific and distinguish from sibling tools like postCryptoLoanFixedBorrowOrderCancel.

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 on when to use this tool versus alternatives such as cancelOrder, cancelAllOrders, or other crypto loan cancel tools. No mention of prerequisites or conditions.

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/bybit-exchange/trading-mcp'

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