Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Search Ecos Statistic

search_ecos_statistic
Read-onlyIdempotent

Retrieve Bank of Korea ECOS economic statistics by specifying a statistical table code, item codes, cycle, and date range for analysis.

Instructions

ECOS 통계표를 코드로 직접 조회합니다 (고급). 통계표·항목 코드는 ECOS 개발 가이드에서 확인합니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stat_code": "<stat_code>",
      "cycle": "<cycle>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "search_ecos_statistic"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes종료 시점 (start 와 같은 형식)
cycleYes주기: A 연 / S 반년 / Q 분기 / M 월 / SM 반월 / D 일
startYes시작 시점 (A: 2020, Q: 2020Q1, M: 202001, D: 20200101)
max_rowsNo
stat_codeYes통계표 코드 (예: 901Y009 소비자물가지수)
item_code1No통계항목 코드1 (생략하면 전체)
item_code2No통계항목 코드2

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety and network profile is covered by structured data. The description adds the useful behavioral fact that valid codes must be sourced externally from the ECOS guide, but says nothing about truncation via max_rows (default 100, cap 1000) or what happens on an invalid code.

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 purpose and then the prerequisite for obtaining codes; no filler. It is efficient, though the second sentence is a prerequisite note rather than additional actionable detail.

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?

With an output schema and rich annotations the description need not explain return values, but for a 7-parameter, 4-required tool it is thin: the code source is referenced vaguely as 'ECOS 개발 가이드' with no location, result-size limits are unmentioned, and the relationship to the simpler sibling tool is left implicit.

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 86%, and the schema itself documents cycle enums, per-cycle date formats, stat_code examples and item_code optionality far better than the description does. The description's only parameter guidance is the pointer to look up table and item codes in the ECOS development guide, which is real but marginal added meaning.

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: querying ECOS statistical tables directly by code, and flags it as '(고급)' advanced usage. That distinguishes it in spirit from the simpler get_key_statistics sibling, but it never names that sibling or states the contrast explicitly.

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?

The '(고급)' tag and the note that codes must be obtained from the ECOS development guide imply this is the low-level path for users who already know codes, but there is no explicit when-to-use rule, no when-not condition, and no named alternative to defer to.

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