Skip to main content
Glama
Sign In
korea-opendata-mcp

korea-opendata-mcp

by myungwoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Key Statistics

get_key_statistics
Read-onlyIdempotent

Retrieve current values for the Bank of Korea's 100 key economic indicators—such as exchange rates, interest rates, inflation, GDP, employment, and stocks—and filter by category.

Instructions

한국은행 100대 통계지표(최신값)를 조회합니다. 환율·금리·물가·GDP·고용 등 주요 경제지표를 한 번에 볼 수 있습니다.

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_key_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo분류명 일부로 필터 (예: 환율, 금리, 물가, 고용, 성장률, 주식). 생략하면 전체 100개

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety and repeatability are covered by structured fields. The description's genuinely additive contribution is the '최신값' (latest value) scoping, which signals this returns current snapshots rather than historical series. It says nothing about freshness latency, caching, or coverage gaps, and the output schema carries the return shape.

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?

Two short sentences, front-loaded with the data source and scope, and the second sentence efficiently conveys breadth of coverage. The indicator list partly repeats the implied scope but earns its place by naming concrete categories an agent can map to the category filter. No filler or hedging.

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 read-only, single-optional-parameter lookup with a full output schema and complete annotation coverage, the description supplies enough to select and invoke the tool: source, scope, latest-value semantics, and coverage breadth. The missing piece is routing guidance against closely related sibling tools, which is a usage concern rather than a definitional gap.

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%, so the single optional 'category' parameter, its partial-match semantics, its 30-character limit, its examples, and the default of all 100 indicators are all documented in the schema. The description adds no syntax or behavior beyond that, which is the expected baseline when the schema does the work.

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 states a specific verb and resource: retrieving the Bank of Korea's 100 key statistical indicators at their latest values, with examples of the coverage (exchange rate, interest rate, prices, GDP, employment). An agent can tell what the tool returns. It does not, however, distinguish itself from overlapping siblings like get_base_rate, get_exchange_rate_history, or get_weather_now, so sibling differentiation is absent.

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: the phrase about seeing major economic indicators '한 번에' (at once) suggests this is the aggregated snapshot tool for a broad overview rather than a single-indicator or historical query. There is no explicit statement of when to prefer it over get_exchange_rate_history or get_base_rate, and no exclusions or prerequisites are given.

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

Deploy Server

Other Tools