Skip to main content
Glama
DrFirstLee

KIMP MCP Server

by DrFirstLee

get_crypto_price

Retrieve KRW prices for cryptocurrencies from Bithumb exchange to analyze Kimchi Premium (KIMP) data and compare Korean versus international market rates.

Instructions

Bithumb에서 특정 암호화폐의 KRW 가격을 조회합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo암호화폐 심볼 (예: BTC, ETH, USDT)BTC

Implementation Reference

  • Handler for the 'get_crypto_price' tool. Extracts symbol from arguments, fetches price using bithumbPrice helper, and returns a formatted text response with the price information.
    case 'get_crypto_price': {
      const symbol = args?.symbol || 'BTC';
      const price = await bithumbPrice(symbol, 'KRW');
      result = {
        success: true,
        symbol: symbol.toUpperCase(),
        price: price,
        timestamp: new Date().toISOString(),
      };
      
      return {
        content: [
          {
            type: 'text',
            text: `💰 ${symbol.toUpperCase()} 가격 (Bithumb)\n\n${price.toLocaleString('ko-KR')} KRW\n\n⏰ ${new Date().toLocaleString('ko-KR')}`,
          },
        ],
      };
    }
  • index.js:154-168 (registration)
    Registration of the 'get_crypto_price' tool in the list of available tools, including name, description, and input schema.
    {
      name: 'get_crypto_price',
      description: 'Bithumb에서 특정 암호화폐의 KRW 가격을 조회합니다.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: '암호화폐 심볼 (예: BTC, ETH, USDT)',
            default: 'BTC',
          },
        },
        required: [],
      },
    },
  • Helper function that fetches the cryptocurrency price from the Bithumb API using axios.
    async function bithumbPrice(symbol = 'BTC', fiat = 'KRW') {
      const pair = `${symbol.toUpperCase()}_${fiat.toUpperCase()}`;
      const url = `https://api.bithumb.com/public/ticker/${pair}`;
    
      try {
        const response = await axios.get(url, { timeout: 5000 });
        const data = response.data;
    
        if (data.status !== '0000') {
          throw new Error(`Bithumb error: ${JSON.stringify(data)}`);
        }
    
        const price = data.data.closing_price;
        return parseFloat(price);
      } catch (error) {
        throw new Error(`Bithumb API 오류: ${error.message}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it indicates this is a read operation ('조회합니다'), it doesn't describe potential behaviors like rate limits, error conditions, authentication needs, or what happens with invalid symbols. For a tool with zero 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 a single, efficient sentence in Korean that directly states the tool's function without unnecessary words. It's appropriately sized for a simple price lookup tool and front-loads the essential information (action, resource, source, currency).

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 low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral details and usage context. Without annotations or output schema, the agent must rely on the description alone, which is incomplete for fully informed tool selection.

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 input schema has 100% description coverage, with the 'symbol' parameter clearly documented in the schema itself. The description doesn't add any parameter-specific information beyond what's in the schema. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even without parameter details in the description.

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: '조회합니다' (retrieves/checks) the KRW price of a specific cryptocurrency from Bithumb. It specifies the resource (cryptocurrency price), source (Bithumb), and currency (KRW). However, it doesn't explicitly distinguish this from sibling tools like 'get_exchange_rate' or 'get_kimp' which likely serve different financial data purposes.

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 mention sibling tools, suggest scenarios for its use, or indicate any prerequisites or exclusions. The agent must infer usage from the purpose alone without explicit 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/DrFirstLee/kimp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server