Skip to main content
Glama
zereight

Bithumb MCP Server

post_wallet_address

Retrieve cryptocurrency deposit wallet addresses for your Bithumb exchange account to receive funds securely.

Instructions

Get member's coin deposit wallet address (Private)

Input Schema

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

Implementation Reference

  • The core handler function that executes the logic for posting to retrieve the wallet address from Bithumb API using requestInfo.
    public async postWalletAddress(
      coinCode?: string,
    ): Promise<IPostWalletAddress> {
      const params = {
        currency: coinCode || 'BTC',
      };
      const res = <IPostWalletAddress>(
        await this.requestInfo('wallet_address', params)
      );
      return res;
    }
  • src/index.ts:147-155 (registration)
    Registers the post_wallet_address tool in the MCP tools list with description and input schema.
      name: 'post_wallet_address',
      description: 'Get member\'s coin deposit wallet address (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)', default: 'BTC' }
        }
      }
    },
  • Handles the tool call by dispatching to the bithumbApi.postWalletAddress implementation.
    case 'post_wallet_address':
      result = await this.bithumbApi.postWalletAddress(args.coinCode as string);
      break;
  • Defines the TypeScript interface for the response of postWalletAddress.
    export interface IPostWalletAddress extends IBithumbResponse {
      data: IWallerAddress;
    }
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 mentions 'Private', hinting at sensitive data, but doesn't disclose behavioral traits like authentication requirements, rate limits, or whether this is a read-only operation. This is inadequate for a tool handling private wallet addresses.

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 front-loaded with the core purpose, but the parenthetical '(Private)' is ambiguous and could be more clearly integrated. It avoids unnecessary words, though it lacks structural elements like examples or caveats.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., address format, associated metadata), behavioral aspects like error handling, or how it fits with sibling tools, making it insufficient for safe and effective 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?

Schema description coverage is 100%, so the schema already documents the 'coinCode' parameter. The description adds no additional meaning beyond what the schema provides, such as explaining why this parameter is needed or how it affects the wallet address retrieval.

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 the action ('Get') and resource ('member's coin deposit wallet address'), but is vague about what 'Private' means and doesn't differentiate from siblings like 'post_account' or 'post_withdrawal_coin' that might also involve wallet operations. It specifies the purpose but lacks precision about scope and uniqueness.

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. With siblings like 'get_balance' or 'post_withdrawal_coin', there's no indication of prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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