Skip to main content
Glama

Open Meteo Air Quality

open_meteo_air_quality
Read-onlyIdempotent

"Air quality / AQI in [city]" / "is the air safe to breathe in [location]" / "pollution levels for [place]" / "smoke / smog / wildfire-smoke forecast" / "pollen forecast", global air quality and pollen forecast at any lat/lng. Returns PM2.5, PM10, ozone (O3), NO2, SO2, CO, dust, and pollen (alder/birch/grass/mugwort/olive/ragweed) up to 5 days ahead, plus European AQI / US AQI. Free, keyless.

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": {
      "latitude": 40.7128,
      "longitude": -74.006
    },
    "name": "open_meteo_air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourlyNoComma-separated variables. Default pm2_5,pm10,o3,no2,european_aqi
latitudeYes
longitudeYes
forecast_daysNo1-5 (default 5)

Output Schema

NameRequiredDescriptionDefault
hourlyNoHourly air quality data
latitudeNoQuery latitude
timezoneNoIANA timezone string
elevationNoElevation of the location in meters
longitudeNoQuery longitude
hourly_unitsNoUnits for hourly air quality variables
generationtime_msNoAPI response generation time in milliseconds
utc_offset_secondsNoUTC offset in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 genuinely non-redundant behavior: global coverage at any lat/lng, a 5-day horizon, the exact variable set, and the fact that it is free and keyless (no auth setup required). It does not discuss rate limits beyond 'free, keyless'.

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 dense paragraph: trigger phrases first, then capability, then return set, then access terms. No filler sentences, and the most decision-relevant information (what it forecasts, horizon, free/keyless) is front-loaded.

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, so return values need not be spelled out, yet the description still summarizes them usefully. The one real gap for a 4-parameter geo tool is guidance on sourcing latitude/longitude (geocoding), which the description omits entirely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema coverage, the description compensates by enumerating the variable values that the free-form 'hourly' string accepts (pm2_5, pm10, o3, no2, so2, co, dust, pollen species) and by stating the 5-day ceiling that bounds 'forecast_days'. Latitude/longitude remain undocumented in both places, but they are self-evident.

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 / AQI / pollen forecast) and enumerates exactly what is returned (PM2.5, PM10, O3, NO2, SO2, CO, dust, six pollen types, European and US AQI). It is clearly an air-quality query tool, distinguishable in substance from open_meteo_forecast, though it never states that contrast explicitly.

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?

The quoted trigger phrases ('is the air safe to breathe in [location]', 'smoke / smog / wildfire-smoke forecast') give good implied usage context. However, there is no when-not-to-use guidance and no routing to siblings — notably no mention of open_meteo_geocode despite latitude/longitude being required, which is the main practical stumbling block for an agent.

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.