Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_coin_balance

Retrieve the balance of a specific cryptocurrency coin across different account types including UNIFIED, CONTRACT, SPOT, and FUND.

Instructions

Get the balance of a specific coin in a specific account type.

Args: coin: The cryptocurrency symbol, e.g., BTC. account_type: Account type: UNIFIED, CONTRACT, SPOT, FUND (default: UNIFIED).

Returns: Coin balance details.

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": {
      "coin": "<coin>"
    },
    "name": "get_coin_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYes
account_typeNoUNIFIED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

The description correctly implies a read-only operation but lacks details on permissions, rate limits, or error conditions. Since no annotations are provided, the description carries full burden but adds minimal behavioral context.

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 succinct, using a standard Args/Returns format, with no unnecessary words. The main purpose is front-loaded.

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?

Return details are vague ('Coin balance details'). Given no output schema, more specifics would be helpful. The tool is simple, but completeness is average.

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

Parameters5/5

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

The description provides clear explanations and examples for both parameters, compensating for the 0% schema description coverage. It defines the coin symbol format and lists valid account types with a default.

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 retrieves the balance of a specific coin for a given account type, distinguishing it from related tools like get_all_coins_balance.

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 like get_account_balance or get_all_coins_balance. Only a default value for account_type is mentioned.

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