Skip to main content
Glama
zereight

Bithumb MCP Server

get_btci

Retrieve Bithumb Index (BTMI, BTAI) data to monitor cryptocurrency market performance and trends on the Bithumb exchange.

Instructions

Get Bithumb Index (BTMI, BTAI) information (Public)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_btci' tool. It makes a GET request to Bithumb's public 'btci' endpoint and returns the typed response.
    public async getBtci(): Promise<IGetBtci> {
      const res = <IGetBtci>await this.requestPublic('btci');
      return res;
    }
  • src/index.ts:309-311 (registration)
    MCP tool dispatch registration: handles 'get_btci' calls by invoking the Bithumb API method.
    case 'get_btci':
      result = await this.bithumbApi.getBtci();
      break;
  • src/index.ts:107-111 (registration)
    Tool metadata registration: defines name, description, and input schema (empty object) for listing in MCP tools.
    {
      name: 'get_btci',
      description: 'Get Bithumb Index (BTMI, BTAI) information (Public)',
      inputSchema: { type: 'object' } // No parameters
    },
  • TypeScript interface for input/output schema validation of the get_btci response data.
    export interface IGetBtci extends IBithumbResponse {
      data: {
        btai: IBtciData;
        btmi: IBtciData;
        date: string;
      };
    }
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 tool retrieves public information, which implies it's likely read-only and non-destructive, but doesn't confirm this or describe other traits like rate limits, error handling, or response format. This leaves significant gaps for a 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded in a single sentence, with no wasted words. It efficiently communicates the core purpose and public nature, making it easy to scan and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose and public scope, yet lacks details on what specific index information is returned, how it's structured, or any behavioral nuances, leaving room for improvement in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, meaning there's no parameter documentation needed. The description adds value by clarifying the tool fetches index information (BTMI, BTAI) without requiring inputs, which is helpful context beyond the empty schema. A baseline of 4 is appropriate for zero-parameter tools.

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 tool's purpose with a specific verb ('Get') and resource ('Bithumb Index (BTMI, BTAI) information'), and specifies it's for public data. However, it doesn't explicitly differentiate from sibling tools like 'get_ticker' or 'get_orderbook' that also retrieve public market data, which prevents a perfect score.

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 minimal guidance by indicating this is for 'Public' information, which might imply it doesn't require authentication unlike some sibling tools (e.g., 'post_account'). However, it lacks explicit when-to-use instructions, alternatives, or context about how this tool differs from other data-retrieval siblings, leaving usage unclear.

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