Skip to main content
Glama
zereight

Bithumb MCP Server

get_orderbook

Retrieve real-time order book data for cryptocurrencies on Bithumb exchange to analyze market depth and trading opportunities.

Instructions

Get order book information (Public)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinCodeYesCryptocurrency symbol (e.g. BTC, ETH)

Implementation Reference

  • Core handler function that fetches the order book data from Bithumb's public API endpoint.
    public async getOrderBook(coinCode: string): Promise<IGetOrderBook> {
      const param = `${coinCode}_${this.paymentCurrency}`;
      const res = <IGetOrderBook>await this.requestPublic('orderbook', param);
      return res;
    }
  • src/index.ts:75-84 (registration)
    Tool registration including name, description, and input schema for listTools.
      name: 'get_orderbook',
      description: 'Get order book information (Public)',
      inputSchema: {
        type: 'object',
        properties: {
          coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['coinCode']
      }
    },
  • MCP server handler that dispatches the get_orderbook tool call to the Bithumb API instance.
    case 'get_orderbook':
      result = await this.bithumbApi.getOrderBook(args.coinCode as string);
      break;
  • TypeScript interface defining the output structure of the getOrderBook response.
    export interface IGetOrderBook extends IBithumbResponse {
      data: {
        timestamp: string;
        order_currency: string;
        payment_currency: string;
        bids: IBidAsks[];
        asks: IBidAsks[];
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. While '(Public)' suggests no authentication is needed, it doesn't disclose rate limits, response format, whether it's real-time or delayed data, or any behavioral constraints. The description adds minimal value beyond the basic operation.

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 at just 5 words, with zero wasted language. It's front-loaded with the core purpose and includes the important '(Public)' qualifier. Every word earns its place.

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 public data retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'order book information' includes (bids/asks, depth levels, timestamps), nor does it address typical concerns like rate limits, data freshness, or response format that would help an agent use it 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?

With 100% schema description coverage, the schema already documents the single 'coinCode' parameter thoroughly. The description adds no additional parameter semantics beyond what's in the schema, so the baseline score of 3 is appropriate.

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 verb ('Get') and resource ('order book information') with the qualifier '(Public)' indicating it's a public data endpoint. However, it doesn't explicitly differentiate from sibling tools like get_ticker or get_candlestick that also retrieve public market data.

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. With multiple sibling tools for market data (get_ticker, get_candlestick) and no indication of what distinguishes order book information from other market data types, the agent receives no 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