Skip to main content
Glama
zereight

Bithumb MCP Server

get_ticker

Fetch real-time cryptocurrency price data from Bithumb exchange to monitor market movements and make informed trading decisions.

Instructions

Get cryptocurrency ticker information (Public)

Input Schema

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

Implementation Reference

  • Core handler implementing the get_ticker tool logic by constructing the endpoint parameter and calling the public Bithumb ticker API via requestPublic.
    public async getTicker(coinCode: string): Promise<IGetTicker> {
      const param = `${coinCode}_${this.paymentCurrency}`;
      const res = <IGetTicker>await this.requestPublic('ticker', param);
      return res;
    }
  • src/index.ts:63-73 (registration)
    MCP tool registration defining the name, description, and input schema for listTools request.
    {
      name: 'get_ticker',
      description: 'Get cryptocurrency ticker information (Public)',
      inputSchema: {
        type: 'object',
        properties: {
          coinCode: { type: 'string', description: 'Cryptocurrency symbol (e.g. BTC, ETH)' }
        },
        required: ['coinCode']
      }
    },
  • MCP CallToolRequestSchema handler case that extracts coinCode from arguments and delegates to bithumbApi.getTicker.
    case 'get_ticker':
      result = await this.bithumbApi.getTicker(args.coinCode as string);
      break;
  • TypeScript interface defining the expected response structure for getTicker (output schema).
    export interface IGetTicker extends IBithumbResponse {
      data: Ticker;
    }
  • Helper function used by getTicker to perform the public GET request to Bithumb API and handle response.
    private async requestPublic(
      endpoint: getEndpointType,
      param?: string,
    ): Promise<IBithumbResponse> {
      const res = <AxiosResponse<IBithumbResponse>>await axios({
        method: 'GET',
        url: `${this.hosts.publicHost}/${endpoint}/${param || ''}`,
      });
      this.checkStatus(res);
      return res.data;
    }
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. While '(Public)' suggests this doesn't require authentication, it doesn't specify rate limits, response format, error conditions, or whether this is a real-time or cached data source. For a data retrieval tool with zero annotation coverage, this leaves significant behavioral gaps.

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 - just 6 words plus a parenthetical. Every element earns its place: the action, resource, and access level are all communicated efficiently with zero wasted words. This is appropriately sized for a simple data retrieval tool.

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 the lack of annotations and output schema, the description should do more to compensate. While the tool appears simple (single parameter, no nested objects), it doesn't explain what 'ticker information' actually returns or how this differs from other data retrieval tools. For a cryptocurrency context with multiple similar tools, this leaves important contextual gaps.

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?

The schema has 100% description coverage, with the single parameter 'coinCode' well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what's already in the schema, so it meets the baseline expectation but doesn't provide additional value regarding parameter usage or constraints.

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 ('cryptocurrency ticker information'), and the parenthetical '(Public)' adds useful context about access level. However, it doesn't explicitly differentiate this from sibling tools like 'post_ticker_user' or explain what 'ticker information' specifically includes compared to other data retrieval tools.

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 that retrieve different types of cryptocurrency data (get_balance, get_candlestick, get_orderbook, etc.), there's no indication of what makes this tool distinct or when it's the appropriate choice over other data retrieval options.

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