Skip to main content
Glama
zereight

Bithumb MCP Server

post_withdrawal_krw

Request a Korean Won withdrawal from your Bithumb exchange account to a specified bank account by providing bank details and amount.

Instructions

Request a KRW withdrawal (Private, Deprecated by Bithumb)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bankYesBank code and name (e.g., 004_은행)
accountYesAccount number
priceYesWithdrawal amount

Implementation Reference

  • Core handler function in ApiBithumb class that executes KRW withdrawal by preparing parameters and calling the internal requestTrade method to POST to Bithumb's /trade/krw_withdrawal endpoint.
    public async postWithdrawalKrw(
      bank: string,
      account: string,
      price: number,
    ): Promise<IPostWithDrawalKrw> {
      const param = {
        bank,
        account,
        price,
      };
      const res = <IPostWithDrawalKrw>(
        await this.requestTrade('krw_withdrawal', param)
      );
      return res;
    }
  • MCP tool input schema definition, specifying parameters bank, account, price with types and descriptions for validation.
    {
      name: 'post_withdrawal_krw',
      description: 'Request a KRW withdrawal (Private, Deprecated by Bithumb)',
      inputSchema: {
        type: 'object',
        properties: {
          bank: { type: 'string', description: 'Bank code and name (e.g., 004_은행)' },
          account: { type: 'string', description: 'Account number' },
          price: { type: 'number', description: 'Withdrawal amount' }
        },
        required: ['bank', 'account', 'price']
      }
    }
  • src/index.ts:392-398 (registration)
    Registration in the CallToolRequestSchema handler switch statement, mapping the tool name to the bithumbApi.postWithdrawalKrw call.
    case 'post_withdrawal_krw':
      result = await this.bithumbApi.postWithdrawalKrw(
        args.bank as string,
        args.account as string,
        args.price as number
      );
      break;
  • TypeScript interface for the output response of postWithdrawalKrw, extending the base Bithumb response type.
    import { IBithumbResponse } from './bithumb-response.interface.js';
    
    export interface IPostWithDrawalKrw extends IBithumbResponse {}
  • src/index.ts:274-286 (registration)
    Tool definition registered in the tools array for ListToolsRequestSchema, including name, description, and input schema.
    {
      name: 'post_withdrawal_krw',
      description: 'Request a KRW withdrawal (Private, Deprecated by Bithumb)',
      inputSchema: {
        type: 'object',
        properties: {
          bank: { type: 'string', description: 'Bank code and name (e.g., 004_은행)' },
          account: { type: 'string', description: 'Account number' },
          price: { type: 'number', description: 'Withdrawal amount' }
        },
        required: ['bank', 'account', 'price']
      }
    }
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' and 'Deprecated', hinting at access restrictions and obsolescence, but fails to disclose critical behavioral traits like authentication requirements, rate limits, irreversible nature of withdrawals, or response format. This leaves significant gaps for a financial transaction tool.

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 very concise with a single phrase, front-loading the core purpose. However, it could be more structured by separating the purpose from the deprecated note for clarity, though it remains efficient with zero wasted words.

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 tool with no annotations and no output schema, the description is inadequate. It lacks details on behavioral aspects (e.g., security, effects), response handling, and usage context, leaving the agent with insufficient information to invoke it safely and effectively.

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 fully documents the three parameters (bank, account, price). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, meeting the baseline for high 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 KRW withdrawal') and specifies the currency (KRW), which distinguishes it from sibling tools like 'post_withdrawal_coin'. However, it doesn't specify the target resource (e.g., from a Bithumb account to a bank account), making it slightly less specific than ideal.

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 'Deprecated by Bithumb', which implies this tool should not be used in favor of newer alternatives, but it doesn't explicitly state when to use it or name specific alternatives. No guidance is provided on prerequisites or context for usage.

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