Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Get Air Quality

get_air_quality
Read-onlyIdempotent

Retrieve real-time PM10 and PM2.5 measurements by Korean province or city, with regional averages and air-quality grades. Check current pollution levels for a specified area or station.

Instructions

미세먼지(PM10·PM2.5)와 대기질을 시도별 실시간 측정값으로 조회합니다. 시도 평균과 등급을 함께 돌려줍니다.

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": {
      "region": "<region>"
    },
    "name": "get_air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes시도명(서울, 경기, 부산 …) 또는 도시명(수원, 강릉 …, 해당 시도로 조회)
stationNo측정소명 일부 (예: 종로구, 중구). 생략하면 시도 전체 요약

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, idempotentHint, non-destructive, and openWorldHint, so the safety profile is covered by structured data. The description only adds that results are real-time and aggregated with a grade; it says nothing about rate limits, data freshness delay, or coverage gaps for missing stations.

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 with zero filler, front-loading the measured pollutants before the aggregation level. Nothing is redundant, though it is arguably terse enough to leave scope questions open.

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 low-complexity two-parameter read tool with a full output schema and complete annotations, the description covers purpose, real-time scope, aggregation level, and return content. Only the edge case of how missing/unmeasured stations are reported 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%: the schema itself explains that region accepts a province or a city name and that station matches a partial station name with omission falling back to the province summary. The description adds no parameter detail beyond this, so 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?

States a specific verb (조회합니다) plus resource (미세먼지 PM10·PM2.5 대기질), the aggregation level (시도별), and what comes back (시도 평균과 등급). It doesn't contrast with any sibling, but its purpose is unambiguous on its own.

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?

'실시간 측정값' implies current/real-time readings rather than historical data, which is useful scoping, but there is no explicit when-to-use statement, no prerequisites, and no mention of the nearby get_weather_now or other sibling as an alternative.

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