Skip to main content
Glama
zereight

Bithumb MCP Server

post_withdrawal_coin

Withdraw cryptocurrency from your Bithumb exchange account by specifying the amount, destination address, and currency type.

Instructions

Request a coin withdrawal (Private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitsYesWithdrawal quantity
addressYesWithdrawal address
currencyNoCryptocurrency symbol (e.g. BTC, ETH)BTC
destinationNoDestination tag/memo (optional, if required)

Implementation Reference

  • Core handler function implementing the post_withdrawal_coin tool logic by preparing parameters and calling the Bithumb trade API for coin withdrawal.
    public async postWithdrawalCoin(
      units: number,
      address: string,
      currency = 'BTC',
      desination?: string,
    ): Promise<IPostWithdrawalCoin> {
      const param = {
        units,
        address,
        currency,
        desination,
      };
      const res = <IPostWithdrawalCoin>(
        await this.requestTrade('btc_withdrawal', param)
      );
      return res;
    }
  • src/index.ts:260-273 (registration)
    Tool registration including name, description, and input schema definition for post_withdrawal_coin.
    {
      name: 'post_withdrawal_coin',
      description: 'Request a coin withdrawal (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          units: { type: 'number', description: 'Withdrawal quantity' },
          address: { type: 'string', description: 'Withdrawal address' },
          currency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)', default: 'BTC' },
          destination: { type: 'string', description: 'Destination tag/memo (optional, if required)' }
        },
        required: ['units', 'address']
      }
    },
  • MCP tool dispatcher case that invokes the postWithdrawalCoin method on the Bithumb API instance.
    case 'post_withdrawal_coin':
      result = await this.bithumbApi.postWithdrawalCoin(
        args.units as number,
        args.address as string,
        args.currency as string | undefined,
        args.destination as string | undefined
      );
      break;
  • TypeScript interface defining the response shape for post_withdrawal_coin, extending the base Bithumb response.
    export interface IPostWithdrawalCoin extends IBithumbResponse {}
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 the tool is 'Private', hinting at authentication needs, but doesn't specify required permissions, rate limits, whether withdrawals are reversible, confirmation times, or potential fees. For a financial transaction tool, this leaves critical behavioral aspects undocumented.

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

Conciseness5/5

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

The description is extremely concise—just five words—with zero wasted language. It's front-loaded with the core action ('Request a coin withdrawal') and adds a brief qualifier ('Private'). Every word earns its place, making it easy to parse quickly.

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 the complexity of a financial withdrawal operation, no annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects like authentication requirements, transaction irreversibility, processing times, error conditions, or response format. For a tool with significant real-world consequences, this leaves too many gaps.

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 input schema already documents all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify format constraints for 'address' or 'destination', or explain 'units' beyond quantity). This meets the baseline for high schema coverage.

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 action ('Request a coin withdrawal') and specifies it's a private operation, which distinguishes it from public API calls. However, it doesn't explicitly differentiate from sibling tools like 'post_withdrawal_krw' (KRW withdrawal) or 'post_wallet_address' (address generation), leaving some ambiguity about when to choose this specific tool.

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. It doesn't mention prerequisites (e.g., needing sufficient balance), exclusions (e.g., not for fiat withdrawals), or compare it to sibling tools like 'post_withdrawal_krw' for different currency types. The '(Private)' hint implies authentication but doesn't state this explicitly.

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