Skip to main content
Glama
workspace

bybit-mcp-server

by workspace
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_coin_balance

Read-only

Check cryptocurrency coin balance by account type (UNIFIED, CONTRACT, SPOT, etc.) and optionally query transfer safe amount.

Instructions

Query coin balance of a specific account type.

    Args:
        accountType: Account type - UNIFIED, CONTRACT, SPOT, OPTION, FUND
        coin: Coin name
        memberId: UID (required when querying sub UID balance)
        withTransferSafeAmount: Query transfer safe amount (0 or 1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNo
memberIdNo
accountTypeYes
withTransferSafeAmountNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. Description adds meaning for each parameter (e.g., memberId for sub UID, withTransferSafeAmount), which is valuable beyond annotations. Does not describe return format, but output schema covers that.

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?

Description is structured, front-loaded with purpose, and uses a clear Args list. Could be slightly more concise, but overall efficient and well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and the detailed parameter explanations, the description is complete. It covers the tool's operation and input semantics without gaps.

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?

Schema description coverage is 0%, but the description fully explains all four parameters: accountType (with allowed values), coin, memberId (when needed), and withTransferSafeAmount (meaning). Adds significant meaning beyond the input schema.

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?

Description clearly states 'Query coin balance of a specific account type', using a specific verb and resource. It distinguishes from siblings like get_wallet_balance by focusing on coin balance per account type.

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?

Description provides parameter guidance but does not explicitly state when to use this tool vs alternatives. The context is clear, but no exclusions or alternative tool names mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/workspace/bybit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server