Skip to main content
Glama
zereight

Bithumb MCP Server

post_account

Retrieve account details and fee information for a specific cryptocurrency on the Bithumb exchange.

Instructions

Get member account information and fees (Private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinCodeYesCryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

  • src/index.ts:125-135 (registration)
    Registration of the 'post_account' tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'post_account',
      description: 'Get member account information and fees (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['coinCode']
      }
    },
  • MCP tool call handler dispatch for 'post_account', which delegates to the Bithumb API client's postAccount method.
    case 'post_account':
      result = await this.bithumbApi.postAccount(args.coinCode as string);
      break;
  • Core implementation of the postAccount method in the Bithumb API client, which makes an authenticated POST request to the Bithumb /info/account endpoint to retrieve account information and fees.
    public async postAccount(coinCode: string): Promise<IPostAccount> {
      const params = {
        order_currency: coinCode,
      };
      const res = <IPostAccount>await this.requestInfo('account', params);
      return res;
    }
  • TypeScript interface defining the expected response structure for the postAccount API call.
    export interface IPostAccount extends IBithumbResponse {
      data: IAccount;
    }
Behavior2/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. It mentions 'Private' access but doesn't elaborate on authentication requirements, rate limits, error conditions, or what specific 'account information and fees' are returned. For a tool that likely involves sensitive financial data, this lack of detail is a significant gap in transparency.

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 brief and to the point with a single phrase, making it efficient and easy to parse. However, it could be more front-loaded by explicitly stating it's for retrieving account details rather than just 'Get', and the '(Private)' tag might be better integrated into the main purpose statement for clarity.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't specify the format or structure of the returned 'account information and fees', nor does it address potential side effects, error handling, or authentication needs. Given the complexity of financial data retrieval, more context is needed for effective agent use.

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 input schema has 100% description coverage, with 'coinCode' clearly documented as a required cryptocurrency symbol. The description doesn't add any parameter-specific information beyond what the schema provides, such as explaining why this parameter is needed or how it affects the output. Given the high schema coverage, a baseline score of 3 is appropriate.

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

Purpose3/5

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

The description states 'Get member account information and fees' which provides a verb ('Get') and resource ('member account information and fees'), making the purpose understandable. However, it doesn't clearly distinguish this tool from sibling tools like 'get_balance' or 'post_user_transactions' that might also retrieve account-related data, leaving some ambiguity about its specific scope.

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 includes '(Private)' which implies restricted access, but it doesn't specify when to use this tool versus alternatives like 'get_balance' or 'post_user_transactions'. No explicit guidance on prerequisites, context, or exclusions is provided, leaving the agent with minimal direction on appropriate usage scenarios.

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