Skip to main content
Glama
zereight

Bithumb MCP Server

post_order_detail

Retrieve detailed information about a specific cryptocurrency order on the Bithumb exchange using order ID and currency symbol.

Instructions

Get details of a specific member order (Private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesOrder ID
orderCurrencyYesCryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

  • Core implementation of the post_order_detail tool: constructs parameters and calls this.requestInfo('order_detail', param) to fetch order details from Bithumb API.
    public async postOrderDetail(
      orderId: string,
      orderCurrency: string,
    ): Promise<IPostOrderDetail> {
      const param = {
        order_id: orderId,
        order_currency: orderCurrency,
      };
      const res = <IPostOrderDetail>await this.requestInfo('order_detail', param);
      return res;
    }
  • TypeScript interface defining the output structure for the postOrderDetail response (IPostOrderDetail).
    export interface IPostOrderDetail extends IBithumbResponse {
      data: IOrderDetail;
    }
  • src/index.ts:184-194 (registration)
    Tool registration in the MCP server: defines name 'post_order_detail', description, and input schema.
      name: 'post_order_detail',
      description: 'Get details of a specific member order (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          orderId: { type: 'string', description: 'Order ID' },
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['orderId', 'orderCurrency']
      }
    },
  • src/index.ts:352-354 (registration)
    Dispatch handler in CallToolRequestSchema: calls bithumbApi.postOrderDetail for the 'post_order_detail' tool.
    case 'post_order_detail':
      result = await this.bithumbApi.postOrderDetail(args.orderId as string, args.orderCurrency as string);
      break;
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' which hints at authentication needs, but doesn't explicitly state permission requirements, rate limits, or error conditions. The description lacks behavioral details like response format or whether it's idempotent.

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. However, the '(Private)' qualifier could be better integrated or explained. It's efficient but could be slightly more polished.

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 details are returned, error handling, or authentication requirements. For a tool that likely involves sensitive order data, more context is needed.

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 both parameters. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain why both orderId and orderCurrency are required or how they interact). Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool retrieves details of a specific member order, which is a clear purpose. However, it doesn't specify what details are included or how it differs from sibling tools like 'post_orders' (which might list multiple orders). The '(Private)' qualifier adds some context but isn't fully explained.

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. The description doesn't mention prerequisites, when this tool is appropriate, or how it relates to sibling tools like 'post_orders' or 'post_user_transactions'.

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