Skip to main content
Glama
zereight

Bithumb MCP Server

get_candlestick

Retrieve candlestick chart data for cryptocurrency trading analysis on Bithumb exchange. Specify currency pairs and time intervals to access historical price patterns and market trends.

Instructions

Get Candlestick data (Public)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderCurrencyYesCryptocurrency symbol (e.g. BTC, ETH)
paymentCurrencyYesPayment currency (KRW or BTC)
chartIntervalsYesChart interval

Implementation Reference

  • Core implementation of GetCandlestick: fetches raw candlestick data from Bithumb public API endpoint and maps it to structured IGetCandlestickData array.
    public async GetCandlestick(
      orderCurrency: string,
      paymentCurrency: currencyType,
      chartIntervals: Time,
    ): Promise<IGetCandlestickData[]> {
      const endpoint = `/candlestick/${orderCurrency}_${paymentCurrency}`;
      const res = <IGetCandlestick>(
        await this.requestPublic(endpoint, chartIntervals)
      );
    
      const candleData: IGetCandlestickData[] = res.data.map((candle) => ({
        timestamp: candle[0],
        opening_price: candle[1],
        closing_price: candle[2],
        max_price: candle[3],
        min_price: candle[4],
        volume: candle[5],
      }));
    
      return candleData;
    }
  • MCP server tool handler for 'get_candlestick': extracts arguments and calls bithumbApi.GetCandlestick.
    case 'get_candlestick':
      result = await this.bithumbApi.GetCandlestick(
        args.orderCurrency as string,
        args.paymentCurrency as currencyType, // Cast to expected type
        args.chartIntervals as Time // Cast to expected type
      );
      break;
  • src/index.ts:113-124 (registration)
    Tool registration in MCP server: defines name, description, and input schema for 'get_candlestick'.
      name: 'get_candlestick',
      description: 'Get Candlestick data (Public)',
      inputSchema: {
        type: 'object',
        properties: {
          orderCurrency: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' },
          paymentCurrency: { type: 'string', enum: ['KRW', 'BTC'], description: 'Payment currency (KRW or BTC)' }, // Assuming KRW/BTC based on standard usage
          chartIntervals: { type: 'string', enum: ['1m', '3m', '5m', '10m', '30m', '1h', '6h', '12h', '24h'], description: 'Chart interval' } // Assuming standard intervals
        },
        required: ['orderCurrency', 'paymentCurrency', 'chartIntervals']
      }
    },
  • TypeScript interface defining the structure of processed candlestick data returned by the tool.
    export interface IGetCandlestickData {
      timestamp: number;
      opening_price: string;
      closing_price: string;
      max_price: string;
      min_price: string;
      volume: string;
    }
  • TypeScript interface for raw Bithumb API candlestick response.
    export interface IGetCandlestick extends IBithumbResponse {
      /** [timestamp, opening amount, closing amount, max price, min price, volume] */
      data: [number, string, string, string, string, 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 only states that the data is 'Public', implying no authentication requirements, but doesn't cover rate limits, response format, error conditions, or whether it's a read-only operation. For a tool with 3 parameters and no annotation coverage, this leaves significant gaps in understanding how it behaves.

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, making it easy to parse quickly while conveying essential information.

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 tool with 3 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what candlestick data includes (OHLCV values), how results are structured, whether there are pagination or date range limitations, or error handling. The '(Public)' hint is helpful but doesn't compensate for the missing behavioral context needed for effective use.

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 all three parameters with descriptions and enums. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is high, but doesn't provide extra value like explaining relationships between parameters or usage examples.

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 ('Candlestick data') with the qualifier '(Public)' indicating it's publicly accessible data. It distinguishes itself from siblings like get_ticker or get_orderbook by specifying candlestick data, though it doesn't explicitly contrast with them. The purpose is specific but could be more distinctive about what makes candlestick data unique.

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 get_ticker or get_orderbook. It doesn't mention prerequisites, timing considerations, or any context for selecting candlestick data over other market data types. The '(Public)' hint suggests no authentication is needed, but this isn't elaborated.

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