Skip to main content
Glama
DrFirstLee

KIMP MCP Server

by DrFirstLee

get_exchange_rate

Retrieve current USD/KRW exchange rates from Naver to calculate cryptocurrency price differences between Korean and international markets.

Instructions

Naver에서 현재 USD/KRW 환율을 조회합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:45-59 (handler)
    Core handler function that fetches USD/KRW exchange rate from Naver API via axios.get and parses the response.
    async function getExchangeRate() {
      const url =
        'https://m.search.naver.com/p/csearch/content/qapirender.nhn?key=calculator&pkid=141&q=%ED%99%98%EC%9C%A8&where=m&u1=keb&u6=standardUnit&u7=0&u3=USD&u4=KRW&u8=down&u2=1';
    
      try {
        const response = await axios.get(url, { timeout: 5000 });
        const data = response.data;
    
        // 환율 값 추출 (콤마 제거)
        const krwValue = parseFloat(data.country[1].value.replace(/,/g, ''));
        return krwValue;
      } catch (error) {
        throw new Error(`환율 API 오류: ${error.message}`);
      }
    }
  • index.js:146-153 (registration)
    Registers the get_exchange_rate tool in the MCP ListTools response with name, description, and empty input schema.
    {
      name: 'get_exchange_rate',
      description: 'Naver에서 현재 USD/KRW 환율을 조회합니다.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • MCP CallToolRequestSchema handler case that calls getExchangeRate, processes result, and returns formatted text response.
    case 'get_exchange_rate': {
      const rate = await getExchangeRate();
      result = {
        success: true,
        exchangeRate: rate,
        timestamp: new Date().toISOString(),
      };
      
      return {
        content: [
          {
            type: 'text',
            text: `💱 현재 USD/KRW 환율\n\n${rate.toLocaleString('ko-KR', { minimumFractionDigits: 2, maximumFractionDigits: 2 })} 원\n\n⏰ ${new Date().toLocaleString('ko-KR')}`,
          },
        ],
      };
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the data source (Naver) and that it retrieves current rates, but doesn't mention potential limitations like rate limits, authentication requirements, data freshness guarantees, or error conditions. For a read-only tool with no parameters, this provides basic behavioral context but lacks important operational details.

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 Korean sentence that front-loads all essential information: source (Naver), action (retrieve), resource (USD/KRW exchange rate), and temporal aspect (current). Every word earns its place with zero redundancy or unnecessary elaboration.

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?

For a simple, parameterless tool with no output schema, the description provides the core purpose and source. However, it lacks information about return format (what structure/units the rate comes in), potential error cases, or any special considerations for using Naver as a source. The description is minimally adequate but leaves gaps an agent would need to discover through trial.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty parameter structure. No additional parameter information is needed or provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('조회합니다' - retrieves/checks) and resource ('USD/KRW 환율' - USD/KRW exchange rate) from a specific source ('Naver에서' - from Naver). It distinguishes from siblings by specifying it's for traditional currency exchange rates rather than cryptocurrency prices (get_crypto_price) or kimchi premium calculations (get_kimp).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying '현재' (current) exchange rates from Naver, suggesting this is for real-time rate checking. However, it doesn't explicitly state when NOT to use this tool or provide clear alternatives beyond what can be inferred from sibling tool names. The context is clear but lacks explicit exclusion guidance.

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