Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_leveraged_token_info

Retrieve details of leveraged tokens on Bybit. Optionally filter by token abbreviation like BTC3L to get specific token information.

Instructions

Get leveraged token info.

Args: lt_coin: Leveraged token abbreviation, e.g., BTC3L (optional, returns all if empty).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_leveraged_token_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
lt_coinNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, and the description does not mention read-only behavior, auth requirements, or any side effects. For a tool that retrieves info, the lack of an explicit read-only hint is a notable gap.

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 brief (one sentence plus a parameter explanation) and front-loaded with the core purpose. It avoids unnecessary words, though the 'Args:' format is a minor stylistic choice. It could be slightly more structured but is effective.

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?

Given no output schema, the description fails to explain what 'info' is returned (e.g., token details, prices, limits). For a data retrieval tool, this omission reduces completeness, though the simplicity of the tool partially mitigates the gap.

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?

The input schema has zero description coverage, but the tool description adds valuable context: it explains the parameter is a leveraged token abbreviation, provides an example (BTC3L), and clarifies that omitting it returns all tokens. This meaningfully supplements the schema.

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 states 'Get leveraged token info' and explains the parameter abbreviation with an example. The purpose is clear, but it does not differentiate from sibling tools like 'get_leveraged_token_market' or 'get_leveraged_token_order_record', which could also return token info.

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?

The description provides minimal guidance: it notes the parameter is optional and returns all tokens if empty. However, it lacks any indication of when to use this tool versus alternatives (e.g., market data vs. order records), nor does it specify prerequisites or exclusions.

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