Open-Meteo MCP Server

Air Quality

air_quality

Read-onlyIdempotent

Fetch air quality forecasts for any coordinates, including PM2.5, PM10, ozone, pollen, AQI, and UV index. Use it to check pollution and allergy risks by location and time.

Instructions

Get air quality forecast data including PM2.5, PM10, ozone, nitrogen dioxide, pollen, European/US AQI indices, UV index and other pollutants.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hourly`	No
`current`	No	Variables to return for the current time.
`domains`	No	"cams_europe": higher resolution, Europe only. "cams_global": worldwide, coarser. "auto" (default) uses Europe where available.
`end_date`	No	Date in YYYY-MM-DD format.
`latitude`	Yes
`timezone`	No	IANA time zone (e.g. "Europe/Paris"), or "auto" for the location's own. Default GMT.
`longitude`	Yes
`past_days`	No	Days before today to include, in addition to the forecast.
`start_date`	No	Date in YYYY-MM-DD format.
`timeformat`	No		iso8601
`forecast_days`	No	Days to forecast, starting today.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv2.5.0Sep 28, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / current

Added value: +{
+  "description": "Variables to return for the current time.",
+  "items": {
+    "enum": [
+      "european_aqi",
+      "us_aqi",
+      "pm10",
+      "pm2_5",
+      "carbon_monoxide",
+      "nitrogen_dioxide",
+      "sulphur_dioxide",
+      "ozone",
+      "aerosol_optical_depth",
+      "dust",
+      "uv_index",
+      "uv_index_clear_sky",
+      "ammonia",
+      "alder_pollen",
+      "birch_pollen",
+      "grass_pollen",
+      "mugwort_pollen",
+      "olive_pollen",
+      "ragweed_pollen"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / domains

Added value: +{
+  "description": "\"cams_europe\": higher resolution, Europe only. \"cams_global\": worldwide, coarser. \"auto\" (default) uses Europe where available.",
+  "enum": [
+    "auto",
+    "cams_europe",
+    "cams_global"
+  ],
+  "type": "string"
+}

addedInput schema / properties / end_date

Added value: +{
+  "description": "Date in YYYY-MM-DD format.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

removedInput schema / properties / forecast_days / default
```
Removed value: -7
```

changedInput schema / properties / forecast_days / description

Previous value: -"Number of forecast days"New value: +"Days to forecast, starting today."

changedInput schema / properties / forecast_days / maximum
```
Previous value: -16New value: +7
```
changedInput schema / properties / forecast_days / minimum
```
Previous value: -1New value: +0
```
removedInput schema / properties / hourly / description
```
Removed value: -"Air quality variables to retrieve"
```

changedInput schema / properties / hourly / items / enum

Previous value: -[
-  "pm10",
-  "pm2_5",
-  "carbon_monoxide",
-  "nitrogen_dioxide",
-  "ozone",
-  "sulphur_dioxide",
-  "ammonia",
-  "dust",
-  "aerosol_optical_depth"
-]New value: +[
+  "pm10",
+  "pm2_5",
+  "carbon_monoxide",
+  "nitrogen_dioxide",
+  "ozone",
+  "sulphur_dioxide",
+  "ammonia",
+  "dust",
+  "aerosol_optical_depth",
+  "carbon_dioxide",
+  "methane",
+  "alder_pollen",
+  "birch_pollen",
+  "grass_pollen",
+  "mugwort_pollen",
+  "olive_pollen",
+  "ragweed_pollen",
+  "european_aqi",
+  "european_aqi_pm2_5",
+  "european_aqi_pm10",
+  "european_aqi_nitrogen_dioxide",
+  "european_aqi_ozone",
+  "european_aqi_sulphur_dioxide",
+  "us_aqi",
+  "us_aqi_pm2_5",
+  "us_aqi_pm10",
+  "us_aqi_nitrogen_dioxide",
+  "us_aqi_ozone",
+  "us_aqi_sulphur_dioxide",
+  "us_aqi_carbon_monoxide",
+  "uv_index",
+  "uv_index_clear_sky",
+  "formaldehyde",
+  "glyoxal",
+  "non_methane_volatile_organic_compounds",
+  "pm10_wildfires",
+  "peroxyacyl_nitrates",
+  "secondary_inorganic_aerosol",
+  "residential_elementary_carbon",
+  "total_elementary_carbon",
+  "pm2_5_total_organic_matter",
+  "sea_salt_aerosol",
+  "nitrogen_monoxide",
+  "is_day"
+]

removedInput schema / properties / latitude / description
```
Removed value: -"Latitude in WGS84 coordinate system"
```
removedInput schema / properties / longitude / description
```
Removed value: -"Longitude in WGS84 coordinate system"
```

changedInput schema / properties / past_days / description

Previous value: -"Include past days data"New value: +"Days before today to include, in addition to the forecast."

changedInput schema / properties / past_days / maximum
```
Previous value: -7New value: +92
```
changedInput schema / properties / past_days / minimum
```
Previous value: -1New value: +0
```

addedInput schema / properties / start_date

Added value: +{
+  "description": "Date in YYYY-MM-DD format.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / timeformat

Added value: +{
+  "default": "iso8601",
+  "enum": [
+    "iso8601",
+    "unixtime"
+  ],
+  "type": "string"
+}

changedInput schema / properties / timezone / description

Previous value: -"Timezone for timestamps"New value: +"IANA time zone (e.g. \"Europe/Paris\"), or \"auto\" for the location's own. Default GMT."

First observedv1.1.3Jan 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the pollutant variable inventory, which is useful, but says nothing about forecast horizon limits, spatial coverage of the domains, or default behavior.

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 front-loaded sentence that opens with the core verb and resource before the pollutant list. No filler, though the exhaustive enumeration is slightly longer than needed to convey the purpose.

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?

For an 11-parameter tool with 64% schema coverage and no output schema, the description covers the 'what data' dimension acceptably but leaves temporal controls (hourly vs current, forecast_days, past_days, start/end_date) and domain trade-offs unexplained beyond the schema text.

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 64%, so the schema documents domains, dates, timezone, past_days and forecast_days itself. The description's pollutant list largely duplicates the hourly/current enums and adds no meaning about key distinctions such as hourly vs current, timeformat, or domain selection.

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 ('Get') and resource ('air quality forecast data') and enumerates the returned pollutant categories (PM2.5, PM10, ozone, NO2, pollen, AQI, UV). This clearly separates it from the weather-forecast siblings, though it never names an alternative to contrast against.

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

Usage Guidelines2/5

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

No guidance on when to choose this tool over weather_forecast or seasonal_forecast, no prerequisites, and no exclusions. The agent must infer scope entirely from the resource name.

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

Deploy Server

Air Quality

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools