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

korea-opendata-mcp

by myungwoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Base Rate

get_base_rate
Read-onlyIdempotent

Retrieve Bank of Korea base rate monthly trends and change dates for a specified number of recent months.

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

Input Schema

NameRequiredDescriptionDefault
monthsNo최근 몇 개월 (월말 기준)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the safety profile is fully covered by structured data. The description adds useful domain context that the result is a monthly series that also surfaces change points (변경 시점), but says nothing about truncation, source lag, or units.

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?

A single compact sentence with zero filler, and the resource is front-loaded before the returned data shape.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile. For a one-optional-parameter read tool the remaining need is the resource plus data shape, both of which are stated; only the time-scope limit implied by the 240-month maximum 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 100% and the single optional parameter months (default 24, max 240, month-end basis) is fully documented in the schema. The description only implies a monthly window via 월별 추이 and adds no new parameter meaning, so the baseline of 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 states a specific verb (조회합니다) and a specific resource (한국은행 기준금리) plus the shape of the data returned (월별 추이와 변경 시점). It is clearly distinguishable from the weather, holiday and subway siblings, though it does not explicitly contrast itself with rate-adjacent tools like get_exchange_rate_history or get_key_statistics.

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 base-rate trend questions because the resource is named. There is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative for related economic series.

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