Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Get Exchange Rate History

get_exchange_rate_history
Read-onlyIdempotent

Retrieve daily Bank of Korea exchange-rate history for USD, JPY, EUR, GBP, or CNY over a chosen date range to analyze currency trends; weekends and holidays are excluded.

Instructions

한국은행 매매기준율(원화 환율) 일별 시계열을 조회합니다. 영업일 기준이라 주말·공휴일은 빠집니다.

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": "get_exchange_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNo통화. JPY 는 100엔 기준USD
end_dateNo종료일. 기본: 오늘
start_dateNo시작일. 기본: 30일 전

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value by disclosing that observations follow business days and therefore omit weekends and public holidays — a data-shape caveat an agent cannot get from the annotations or schema.

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?

Two sentences, both load-bearing: the first states what is retrieved, the second states the business-day constraint. The purpose is front-loaded and there is no filler.

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?

With a full schema, an output schema, and rich annotations, the definition only needs to add source and shape context, which it does. The remaining gap is minor: it does not state the historical depth of the series or the expected date format, both of which an agent might want.

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?

Schema description coverage is 100%, and the schema already documents currency (including the JPY 100-yen convention), start_date, and end_date with defaults. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 names a specific verb and resource: retrieval of the Bank of Korea's 매매기준율 daily won-denominated exchange-rate time series. That is concrete enough to separate it from the weather, holiday, and subway siblings. It stops short of explicitly contrasting with the closest-sounding sibling, get_base_rate, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for historical daily FX rates, and the business-day note signals the data's granularity. There is no explicit statement of when to prefer it over get_base_rate or an ECOS statistic search, and no mention of the available currency set or default window.

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