Skip to main content
Glama
zereight

Bithumb MCP Server

post_market_buy

Execute a market buy order on Bithumb cryptocurrency exchange to purchase specified cryptocurrency units at current market prices.

Instructions

Place a market buy order (Private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitsYesQuantity to buy
orderCurrencyYesCryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

  • Core handler function implementing the market buy logic by preparing parameters and calling the Bithumb trade API endpoint 'market_buy'.
    public async postMarketBuy(
      units: number,
      orderCurrency: string,
    ): Promise<IPostMarketBuy> {
      const param = {
        units,
        order_currency: orderCurrency,
      };
      const res = <IPostMarketBuy>await this.requestTrade('market_buy', param);
      return res;
    }
  • src/index.ts:237-247 (registration)
    Registers the 'post_market_buy' tool in the MCP server's tools list, including name, description, and input schema.
      name: 'post_market_buy',
      description: 'Place a market buy order (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          units: { type: 'number', description: 'Quantity to buy' },
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['units', 'orderCurrency']
      }
    },
  • MCP server handler that dispatches 'post_market_buy' tool calls to the underlying bithumbApi.postMarketBuy method.
    case 'post_market_buy':
      result = await this.bithumbApi.postMarketBuy(args.units as number, args.orderCurrency as string);
      break;
  • TypeScript interface defining the response structure for the post market buy operation.
    export interface IPostMarketBuy extends IBithumbResponse {
      order_id: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'market buy order' which implies immediate execution at current prices, but doesn't cover critical aspects like authentication requirements, rate limits, transaction fees, order confirmation, or what happens on execution failure. For a financial transaction tool, this is a significant gap.

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 with just 5 words, front-loading the core purpose ('Place a market buy order') and adding only the essential 'Private' qualifier. Every word earns its place with zero waste.

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 this is a financial transaction tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after order placement, return values, error conditions, or security implications. The 'Private' hint is vague without context about authentication or account requirements.

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 both parameters ('units' and 'orderCurrency'). The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but no extra value.

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 ('Place a market buy order') and specifies it's a 'Private' operation, which distinguishes it from public trading functions. However, it doesn't explicitly differentiate from its sibling 'post_market_sell' beyond the buy/sell distinction, which is implied but not stated.

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 like 'post_market_sell' or other order types (e.g., limit orders). It mentions 'Private' but doesn't explain what that means in context or when private vs. public trading is appropriate.

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