Skip to main content
Glama

Seoul Air Quality

seoul_air_quality
Read-onlyIdempotent

Real-time air quality across Seoul districts (자치구), PM10, PM2.5, ozone, NO2, CO, SO2, the comprehensive air index (CAI), and its grade (좋음/Good ... 나쁨/Bad). Use for "air quality in Seoul / ", "Seoul PM2.5 right now".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seoul_air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely useful context via 'real-time' and by decoding the CAI grade scale (좋음/Good ... 나쁨/Bad), but it omits freshness cadence, units, and whether values are live-station or averaged. It also implies district targeting while the tool accepts no parameters, leaving an unresolved question about how a district is selected.

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?

Front-loaded with the core capability, then the pollutant list, then usage triggers — a sensible order with no filler sentences. The pollutant enumeration is long but each item is distinct data, so it earns most of its space.

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 no output schema and no parameters, the description carries the full burden of explaining what comes back and how district-level data is requested. It says nothing about response shape (per-district rows vs. a city aggregate), language of district names, or units. Adequate to identify the tool, incomplete for invoking and interpreting it confidently.

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?

The schema has zero parameters, so the baseline of 4 would normally apply. However, the description explicitly advertises a '<district>' usage form even though no district argument exists, which creates a semantic ambiguity the schema cannot resolve. That inconsistency pulls the score down to 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: real-time air quality across Seoul districts, enumerated by pollutant (PM10, PM2.5, ozone, NO2, CO, SO2) plus the comprehensive air index and its grade. The Seoul-district framing cleanly separates it from siblings like seoul_events and seoul_real_estate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger phrasings ('air quality in Seoul / <district>', 'Seoul PM2.5 right now'), which is real when-to-use guidance rather than a restatement. It doesn't need exclusions because none of the listed siblings overlap in scope, but it offers no note on what to do if the user asks about non-Seoul locations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.