Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Get Weather Forecast

get_weather_forecast
Read-onlyIdempotent

Retrieve a 1–3 day weather forecast for a Korean location by place name or coordinates, summarizing daily low/high temperatures, precipitation probability, and sky conditions; optionally include hourly details.

Instructions

단기예보(최대 3일)를 날짜별 최저/최고기온, 강수확률, 하늘상태로 요약합니다.

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

Input Schema

NameRequiredDescriptionDefault
daysNo예보 일수 (1~3, 오늘 포함)
locationYes지명(서울, 부산, 강릉, 제주, 경기 등) 또는 '위도,경도' (예: 37.5665,126.9780)
include_hourlyNo시간별 예보 포함 여부

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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds what the response summarizes (min/max temperature, precipitation probability, sky condition), which is useful context beyond the annotations, but it says nothing about the optional hourly expansion or how the 3-day cap is enforced.

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 front-loaded sentence with no filler; the scope limit and the returned data are stated before anything else, and every clause earns its place.

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?

An output schema exists and annotations are rich, so the description needn't explain return values or safety. It covers purpose and scope adequately; the only meaningful gap is that it never distinguishes itself from get_weather_now or hints that include_hourly changes the response shape.

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 schema already documents location formats, the 1–3 day range, and include_hourly. The description's '최대 3일' merely echoes the days maximum, so it adds little beyond the structured fields — 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 states a specific verb and resource ('단기예보... 요약합니다') and pins the scope (최대 3일) plus the returned fields (최저/최고기온, 강수확률, 하늘상태). It is clearly a forecast tool rather than a current-conditions tool, though it never names the sibling get_weather_now to make the distinction explicit.

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: '단기예보(최대 3일)' suggests this is for multi-day outlooks rather than present conditions, which indirectly separates it from get_weather_now. There is no explicit when-to-use/when-not statement and no routing to an alternative.

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