Skip to main content
Glama
zereight

Bithumb MCP Server

post_cancel

Cancel cryptocurrency orders on Bithumb exchange by specifying order type, ID, and currency symbol to manage trading positions.

Instructions

Cancel an order (Private)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesOrder type (bid or ask)
orderIdYesOrder ID to cancel
orderCurrencyYesCryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

  • Core handler function that executes the order cancellation logic by preparing parameters and calling the Bithumb trade API's 'cancel' endpoint.
    public async postCancel(
      type: tradeType,
      orderId: string,
      orderCurrency: string,
    ): Promise<IPostCancel> {
      const param = {
        type,
        order_id: orderId,
        order_currency: orderCurrency,
      };
      const res = <IPostCancel>await this.requestTrade('cancel', param);
      return res;
    }
  • src/index.ts:223-235 (registration)
    Registers the 'post_cancel' tool with the MCP server, defining its name, description, and input schema for validation.
    {
      name: 'post_cancel',
      description: 'Cancel an order (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          type: { type: 'string', enum: ['bid', 'ask'], description: 'Order type (bid or ask)' },
          orderId: { type: 'string', description: 'Order ID to cancel' },
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['type', 'orderId', 'orderCurrency']
      }
    },
  • MCP server request handler that dispatches the 'post_cancel' tool call to the underlying Bithumb API method.
    case 'post_cancel':
      result = await this.bithumbApi.postCancel(
        args.type as tradeType, // Cast to expected type
        args.orderId as string,
        args.orderCurrency as string
      );
      break;
  • TypeScript interface defining the expected response structure for the post_cancel operation, extending the base Bithumb response.
    import { IBithumbResponse } from './bithumb-response.interface.js';
    
    export interface IPostCancel 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 states the action ('Cancel') but lacks details on permissions needed, whether cancellation is reversible, rate limits, or response format. The '(Private)' hint adds minimal context, insufficient for a mutation tool with zero annotation coverage.

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 a single, efficient sentence with zero wasted words, making it appropriately concise. However, it could be more front-loaded by integrating the '(Private)' qualifier into the main action for better clarity, slightly affecting structure.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, and return values, which are critical for an agent to invoke 'post_cancel' correctly in a trading context with siblings like 'post_place'.

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 (type, orderId, orderCurrency). The description adds no parameter-specific information beyond what the schema provides, such as examples or constraints, resulting in a baseline score of 3.

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 ('Cancel') and resource ('an order'), with the qualifier '(Private)' suggesting restricted access. However, it doesn't differentiate this tool from potential cancellation alternatives among its siblings, such as 'post_market_buy/sell' which might also affect orders, leaving some ambiguity about its specific scope.

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, prerequisites, or exclusions. Given siblings like 'post_place' (likely for creating orders) and 'post_orders' (possibly for listing), there's no indication of how 'post_cancel' fits into the workflow, leaving usage context implied at best.

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