Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_account_balance

Check the balance of a specific cryptocurrency asset in your Bybit account, with optional account type selection.

Instructions

Get the balance of a specific cryptocurrency asset.

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

Returns: Asset balance info.

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_account_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYes
account_typeNoUNIFIED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Get the balance' without stating that it is a read-only operation, or disclosing any other behavioral traits such as authentication requirements or rate limits.

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 concise and front-loaded, with a clear one-line summary followed by structured Args and Returns sections. Every sentence is necessary.

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 return value is described only as 'Asset balance info', which is too vague to be useful. Since there is no output schema, the description should at least hint at the structure of the balance data (e.g., amount, currency, account type).

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 description adds meaningful semantics beyond the input schema: it explains the 'coin' parameter with an example ('BTC') and enumerates the allowed values for 'account_type' (UNIFIED, CONTRACT, SPOT, FUND). This compensates for the 0% schema description coverage.

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 clearly states the verb 'get' and the resource 'balance of a specific cryptocurrency asset'. However, it does not differentiate itself from the sibling tool 'get_coin_balance', which likely serves a similar purpose.

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 is provided on when to use this tool versus alternatives like 'get_coin_balance' or 'get_all_coins_balance'. No exclusions or context are given.

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