Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Get Weather Now

get_weather_now
Read-onlyIdempotent

Retrieve current weather conditions in South Korea—temperature, humidity, precipitation, and wind—from KMA observations using a city name or latitude/longitude.

Instructions

현재 날씨(초단기실황: 기온, 습도, 강수, 바람)를 조회합니다. 기상청 실측 자료입니다.

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": {
      "location": "<location>"
    },
    "name": "get_weather_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYes지명(서울, 부산, 강릉, 제주, 경기 등) 또는 '위도,경도' (예: 37.5665,126.9780)

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 readOnly, idempotent, openWorld and non-destructive behavior. The description adds that data comes from KMA real observation (실측), which tells the agent it is measured rather than modeled data — useful and not covered by annotations. It says nothing about freshness/staleness, units, or failure modes, though.

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 short sentences, with the returned fields front-loaded and the data source as supporting context. Nothing is redundant or padded.

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 single-parameter read tool with a full-coverage schema, rich annotations, and an output schema defining return values, the description covers purpose, fields, and source adequately. Only the freshness/latency of the '초단기실황' observation is left unstated.

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 there is a single parameter, so the schema already explains the location string and the 'lat,lon' format with an example. The description adds no parameter-level meaning beyond that, which is the baseline expectation.

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?

States a specific verb (조회) and resource (현재 날씨) and enumerates the fields returned (기온, 습도, 강수, 바람). The word 현재 implicitly separates it from the forecast sibling, but no sibling is named explicitly, which keeps it a step short of 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 by the word 현재 ('now'), which suggests it should be chosen over a forecast tool for present conditions. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the routing.

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