Skip to main content
Glama
zereight

Bithumb MCP Server

post_market_sell

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

Instructions

Place a market sell order (Private)

Input Schema

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

Implementation Reference

  • Core handler function that executes the market sell order by constructing parameters and invoking the Bithumb trade API via requestTrade('market_sell').
    public async postMarketSell(
      units: number,
      orderCurrency: string,
    ): Promise<IPostMarketSell> {
      const param = {
        units,
        order_currency: orderCurrency,
      };
    
      const res = <IPostMarketSell>await this.requestTrade('market_sell', param);
      return res;
    }
  • Input schema for the post_market_sell tool, specifying units (number, quantity to sell) and orderCurrency (string, e.g., BTC) as required fields.
    inputSchema: {
      type: 'object',
      properties: {
        units: { type: 'number', description: 'Quantity to sell' },
        orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
      },
      required: ['units', 'orderCurrency']
    }
  • src/index.ts:248-259 (registration)
    Registration of the 'post_market_sell' tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'post_market_sell',
      description: 'Place a market sell order (Private)',
      inputSchema: {
        type: 'object',
        properties: {
          units: { type: 'number', description: 'Quantity to sell' },
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['units', 'orderCurrency']
      }
    },
  • Top-level MCP tool handler switch case that invokes the Bithumb API client's postMarketSell method with parsed arguments.
    case 'post_market_sell':
      result = await this.bithumbApi.postMarketSell(args.units as number, args.orderCurrency as string);
      break;
  • TypeScript interface for the response of post market sell, extending IBithumbResponse and adding order_id field.
    export interface IPostMarketSell 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 but offers minimal behavioral information. It identifies this as a sell operation but doesn't disclose critical details like execution speed, price determination (market vs limit), whether it's immediate or queued, authentication requirements, rate limits, or what happens on execution failure. The '(Private)' tag is unexplained and adds confusion rather than clarity.

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 extremely concise at just 5 words, but the '(Private)' tag feels like unexplained jargon that doesn't earn its place. The core purpose is front-loaded clearly, but the additional tag adds ambiguity without value. Still, it avoids verbosity and gets straight to the point.

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 financial trading tool with no annotations and no output schema, the description is inadequate. It doesn't address critical context like: what market it operates in, execution guarantees, response format, error conditions, or relationship to account balance/authentication. The '(Private)' tag suggests some restriction but doesn't explain it, leaving significant gaps for a tool that performs financial transactions.

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. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain unit conventions (whole coins vs fractions), valid currency symbols beyond the examples, or parameter interactions. Baseline 3 is appropriate when schema does complete documentation.

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 sell order') and specifies the resource type ('order'), though it doesn't explicitly mention cryptocurrency trading context. It distinguishes from sibling 'post_market_buy' by specifying 'sell', but doesn't differentiate from other order-related tools like 'post_place' or 'post_cancel'.

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 explain when to choose market sell vs limit sell (if available), when to use this versus 'post_market_buy', or how it relates to other order management tools like 'post_cancel' or 'post_orders'. The '(Private)' tag is ambiguous and doesn't provide clear usage context.

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