Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_convert_coin_list

Retrieve available coins for crypto-to-crypto conversion on Bybit, with optional filters by account type, coin, and side.

Instructions

Get available coins for crypto-to-crypto conversion.

Args: account_type: UNIFIED or eb_convert_funding. coin: Filter by coin (optional). side: 0: from coin, 1: to coin (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": {
      "account_type": "<account_type>"
    },
    "name": "get_convert_coin_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_typeYes
coinNo
sideNo

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 provided; description lacks disclosure of behavioral traits like idempotency, rate limits, or side effects. Only states 'Get' which implies read-only, but no explicit confirmation.

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?

Concise with a clear intro and arg list; no fluff. However, the arg section could be more structured (e.g., bullet points) for easier parsing, but overall it's efficient.

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?

Lacks output schema and description of return value. For a list tool, it would be helpful to mention that it returns a list of coins. No extra context from annotations.

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?

Schema has 0% description coverage, but the description adds meaning: account_type (UNIFIED/eb_convert_funding), coin (filter), side (0 from, 1 to). This compensates for the schema gaps, though defaults are not explained.

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 'Get available coins for crypto-to-crypto conversion' with specific verb and resource. It distinguishes itself from sibling tools like get_convert_history by focusing on listing coins.

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. No mention of prerequisites or conditions for using this tool vs other get_* or convert tools.

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