Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

redeem_leveraged_token

Redeem leveraged tokens by specifying token symbol and quantity to convert back to the underlying asset.

Instructions

Redeem a leveraged token.

Args: lt_coin: Leveraged token abbreviation, e.g., BTC3L. quantity: Redemption quantity. serial_no: Unique serial number (optional).

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": {
      "lt_coin": "<lt_coin>",
      "quantity": "<quantity>"
    },
    "name": "redeem_leveraged_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
lt_coinYes
quantityYes
serial_noNo

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?

No annotations are provided, so the description must carry behavioral disclosure. It only says 'Redeem' without mentioning side effects, fees, order flow, or whether this is a destructive action. This is insufficient for a financial tool.

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: three lines front-load the purpose and list parameters without extra words. Every sentence serves a purpose.

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?

The description lacks output schema information and does not mention what the response looks like or any confirmation steps. For a redemption action, more context (e.g., successful redemption, balance update) is needed.

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 value by explaining lt_coin as a leveraged token abbreviation with an example, quantity as redemption quantity, and serial_no as optional. However, it does not specify valid values or constraints.

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 the tool redeems a leveraged token, using a specific verb and resource. It distinguishes from the sibling 'purchase_leveraged_token' which is the opposite action.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites like having a leveraged token position. The purpose is implied but not guided.

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