Skip to main content
Glama

get_wallet_balance

Retrieve cryptocurrency wallet balances for Bybit trading accounts. Specify account type and optional coin to check available funds for trading operations.

Instructions

Get wallet balance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountTypeYesAccount type (UNIFIED, CONTRACT, SPOT)
coinNoCoin symbol

Implementation Reference

  • MCP tool handler case that invokes the BybitService.getWalletBalance method with provided arguments and formats the response as JSON text content.
    case 'get_wallet_balance': {
      const result = await this.bybitService.getWalletBalance(typedArgs.accountType, typedArgs.coin);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the get_wallet_balance tool, specifying accountType as required and coin as optional.
    inputSchema: {
      type: 'object',
      properties: {
        accountType: {
          type: 'string',
          description: 'Account type (UNIFIED, CONTRACT, SPOT)',
        },
        coin: {
          type: 'string',
          description: 'Coin symbol',
        },
      },
      required: ['accountType'],
  • src/index.ts:139-155 (registration)
    Tool registration entry in the ListTools response, including name, description, and input schema.
    {
      name: 'get_wallet_balance',
      description: 'Get wallet balance',
      inputSchema: {
        type: 'object',
        properties: {
          accountType: {
            type: 'string',
            description: 'Account type (UNIFIED, CONTRACT, SPOT)',
          },
          coin: {
            type: 'string',
            description: 'Coin symbol',
          },
        },
        required: ['accountType'],
      },
  • Core implementation of wallet balance retrieval using Bybit V5 API endpoint /v5/account/wallet-balance, constructing parameters and making authenticated GET request.
    async getWalletBalance(accountType: string, coin?: string): Promise<BybitResponse<{ list: WalletBalance[] }> | { error: string }> {
      const params: any = { accountType };
      if (coin) params.coin = coin;
      return this.makeBybitRequest('/v5/account/wallet-balance', 'GET', params);
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, requires authentication, has rate limits, returns real-time or cached data, or what format the balance information comes in. This is inadequate for a financial data tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just three words, this is under-specification rather than effective brevity. The description fails to provide necessary context about what a 'wallet balance' entails in this trading system, making it inefficient for agent understanding.

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

Completeness1/5

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

For a financial tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain what type of balance is returned (e.g., available balance, total balance, in what currency), doesn't mention authentication requirements, and provides no behavioral context despite the tool's potential complexity in a trading environment.

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

Parameters3/5

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

The schema description coverage is 100%, with both parameters ('accountType' and 'coin') clearly documented in the schema. The description adds no parameter information beyond what the schema already provides, so it meets the baseline for adequate coverage without adding value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get wallet balance' is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what resource is being retrieved (e.g., cryptocurrency wallet balance) or distinguish this tool from potential siblings like 'get_positions' or 'get_tickers' that might also provide financial data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or exclusions, leaving the agent with no usage direction despite having multiple sibling tools in the trading/financial domain.

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/kondisettyravi/mcp-bybit-node'

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