Skip to main content
Glama

환율 조회(월평균·연평균·일별)

exchange_rate
Read-only

Monthly and yearly average exchange rates, plus daily base rates, against the Korean won (KRW) for about 50 major currencies. 원화 기준 주요 통화의 월평균·연평균 환율(month)과 일별 매매기준율(date)을 조회합니다. month 를 생략하면 지난달, date 를 생략하면 오늘이며 둘은 함께 보낼 수 없습니다. 일별은 영업일 기준이고 비영업일이면 직전 영업일 고시를 돌려주며 as_of_date 로 실제 고시일을 알립니다. JPY·IDR·VND 는 100단위(unit=100) 값입니다. [호출당 5포인트]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo조회 일자 YYYYMMDD (예: 20261114). 생략하면 오늘. 일별 매매기준율 조회이며 month 와 함께 보낼 수 없음
monthNo조회 월 YYYYMM (예: 202609). 생략하면 지난달. 이번 달 이후는 조회 불가. date 와 함께 보낼 수 없음
currencyNo통화 코드를 쉼표로 구분 (예: USD,JPY,EUR). 생략하면 전체 통화

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / date
      Added value: +{
      +  "description": "조회 일자 YYYYMMDD (예: 20261114). 생략하면 오늘. 일별 매매기준율 조회이며 month 와 함께 보낼 수 없음",
      +  "type": "string"
      +}
    • changedInput schema / properties / month / description
      Previous value: -"조회 월 YYYYMM (예: 202609). 생략하면 지난달. 이번 달 이후는 조회 불가"New value: +"조회 월 YYYYMM (예: 202609). 생략하면 지난달. 이번 달 이후는 조회 불가. date 와 함께 보낼 수 없음"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnly/openWorld annotations, the description discloses default parameters, mutual exclusivity, non-business-day fallback to the prior business day with as_of_date, 100-unit scaling for JPY/IDR/VND, and a 5-point per-call cost. These are concrete behavioral traits an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is front-loaded and each sentence carries operational detail (defaults, exclusivity, business-day fallback, units, cost). The bilingual repetition of the opening purpose adds length without new information, keeping it from a 5.

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

Completeness4/5

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

For a three-optional-parameter lookup with no output schema, it covers input behavior, edge cases, and one output field (as_of_date) well. It does not describe the full returned rate structure or explain how yearly averages are selected, leaving a modest gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: currency-specific 100-unit handling for JPY/IDR/VND and the ~50-currency scope. Defaults and mutual exclusivity are repeated from the schema rather than newly explained.

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 names a specific operation (exchange-rate lookup) and resource (monthly/yearly averages and daily base rates for about 50 currencies against KRW). It clearly separates monthly and daily modes, so an agent can distinguish this from interest-rate, crypto, or bank-code siblings.

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?

It explains the key selection rule between month and date (mutually exclusive, with defaults of last month and today) and notes business-day handling. It does not name alternative tools or when-not-to-use cases, so it is clear but not fully comparative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.