Skip to main content
Glama

Hava kalitesi

hava_get_air_quality

Retrieve current hourly air quality index, category, and dominant pollutant per station in Türkiye, sorted worst-first, with optional province filtering.

Instructions

Air quality (hava kalitesi, kirlilik, PM10, PM2.5) from Türkiye's National Air Quality Monitoring Network: latest hourly AQI, category and dominant pollutant per station, worst first. Filter by province.

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": "hava_get_air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
ilNoİl adı. Boşsa tüm Türkiye (en kötüden iyiye).
limitNoEn fazla kaç kayıt döndürülsün (1–200, varsayılan 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the upstream source (national monitoring network), data freshness (latest hourly), and result ordering (worst first). It omits operational behavior an agent might care about: whether every province has stations, whether stale readings persist, and any rate or coverage limits.

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?

A single dense sentence with the resource named first and the ordering and filter trailing. Every clause carries information; the multilingual keyword list (hava kalitesi, kirlilik, PM10, PM2.5) is there for matching and is compact.

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 two-parameter, read-only, no-annotation tool with no output schema, the description covers source, freshness, fields returned, ordering, and filtering — enough to call it correctly. Only station coverage and staleness caveats are missing, which are secondary.

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 both parameters are already documented in the schema, including the default nationwide behavior and the 1–200 limit. The description adds only the province-filter hint, which the schema already states, plus an implicit note that 'worst first' ordering is the default view. Baseline 3 is appropriate.

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 names a specific resource (air quality from Türkiye's National Air Quality Monitoring Network) and states the payload precisely: latest hourly AQI, category, and dominant pollutant per station. The 'worst first' ordering is stated explicitly. It never names hava_get_current or hava_get_forecast, so the contrast with those siblings is only implied by 'latest hourly'.

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?

'Filter by province' and the hourly/latest framing imply the when — fetching current station-level air quality readings. There is no explicit when-not, no mention of the forecast sibling as the alternative for future values, and no stated prerequisites.

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