Skip to main content
Glama
zereight

Bithumb MCP Server

get_balance

Retrieve cryptocurrency account balances from Bithumb exchange to monitor holdings and track portfolio value.

Instructions

Get account balance (Private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinCodeNoCryptocurrency symbol (e.g. BTC, ETH) or ALLALL

Implementation Reference

  • Core handler implementation for the get_balance tool. Fetches balance data from Bithumb's info/balance endpoint and refines the response using refineBalance helper.
    public async postBalance(coinCode = 'BTC'): Promise<IPostBalance> {
      const params = {
        currency: coinCode,
      };
      const res = <IBalanceResponse>await this.requestInfo('balance', params);
    
      const data = this.refineBalance(res, coinCode.toLowerCase());
      return data;
    }
  • Helper function used by postBalance to refine and format the raw balance response into the standardized IPostBalance structure.
    private refineBalance(res: IBalanceResponse, coinCode: string) {
      const data: IPostBalance = {
        ...res,
        data: {
          total_coin: res.data[`total_${coinCode}`],
          total_krw: res.data.total_krw,
          in_use_coin: res.data[`in_use_${coinCode}`],
          in_use_krw: res.data.in_use_krw,
          available_coin: res.data[`available_${coinCode}`],
          available_krw: res.data.available_krw,
          xcoin_last_coin: res.data[`xcoin_last_${coinCode}`],
        },
      };
      return data;
    }
  • src/index.ts:137-145 (registration)
    Registration of the get_balance tool in the MCP tools list, including name, description, and input schema.
      name: 'get_balance', // Renamed from postBalance for clarity, as it retrieves data
      description: 'Get account balance (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH) or ALL', default: 'ALL' }
        }
      }
    },
  • MCP tool call handler dispatch for get_balance, invoking the ApiBithumb postBalance method with provided coinCode or default 'ALL'.
    case 'get_balance':
      result = await this.bithumbApi.postBalance(args.coinCode as string || 'ALL');
      break;
Behavior2/5

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

No annotations are provided, so the description carries full burden of behavioral disclosure. The description mentions '(Private)' which hints at authentication requirements, but doesn't explicitly state this. It doesn't disclose rate limits, error conditions, response format, or whether this is a read-only operation. For a financial tool with no annotation coverage, this leaves significant behavioral gaps.

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?

The description is extremely concise at just three words, making it easy to parse. However, the '(Private)' tag could be more clearly integrated or explained. While efficient, it might be too brief given the lack of other context about this financial tool.

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?

For a financial balance retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the balance returns in, whether it includes multiple currencies, authentication requirements, or error handling. Given the complexity of financial tools and complete lack of structured metadata, the description should provide more operational context.

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?

Schema description coverage is 100%, so the schema already fully documents the single parameter. The description doesn't add any parameter-specific information beyond what's in the schema. With one parameter and complete schema coverage, the baseline score of 3 is appropriate as the description doesn't need to compensate for schema gaps.

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 resource 'account balance', making the purpose immediately understandable. It distinguishes from siblings by focusing specifically on balance retrieval rather than other account operations like transactions or orders. However, it doesn't explicitly differentiate from similar-sounding tools like 'get_assets_status'.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools available (like get_assets_status, get_transaction_history, post_account), there's no indication of when balance retrieval is appropriate versus other account information tools. The '(Private)' tag suggests authentication may be needed but doesn't clarify prerequisites.

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/zereight/bithumb-mcp'

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