InfraNode

Air Quality

air_quality

Read-onlyIdempotent

Get official air quality readings (PM10, NO2) for any German city using data from the Umweltbundesamt.

Instructions

Get official air quality for a German city (PM10, NO2 and more).

Sourced from the Umweltbundesamt (UBA). Read-only. For live nearest-station hourly readings use get_city_resource(slug, resource='air') instead.

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": {
      "slug": "<slug>"
    },
    "name": "air_quality"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'.

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.0.1Jul 6, 2026
- removedInput schema / properties / slug / title
```
Removed value: -"Slug"
```
- removedInput schema / title
```
Removed value: -"air_qualityArguments"
```
- removedOutput schema / $defs / ToolMeta / description
```
Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
```
- removedOutput schema / $defs / ToolMeta / properties / attribution / title
```
Removed value: -"Attribution"
```
- removedOutput schema / $defs / ToolMeta / properties / cache_status / title
```
Removed value: -"Cache Status"
```
- removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
```
Removed value: -"Correlation Id"
```
- removedOutput schema / $defs / ToolMeta / properties / license / title
```
Removed value: -"License"
```
- removedOutput schema / $defs / ToolMeta / properties / source / title
```
Removed value: -"Source"
```
- removedOutput schema / $defs / ToolMeta / properties / source_status / title
```
Removed value: -"Source Status"
```
- removedOutput schema / $defs / ToolMeta / title
```
Removed value: -"ToolMeta"
```
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / title
```
Removed value: -"ToolEnvelope"
```

Changed2 schema fields changedJun 25, 2026

addedInput schema / properties / slug / description

Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}

First observedv1.0.0Jun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

While annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, the description adds value by stating the data source (Umweltbundesamt) and the specific pollutants included (PM10, NO2), enriching behavioral context without contradiction.

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?

The description is two sentences long, front-loaded with the main purpose, followed by source and alternative usage. Every sentence serves a clear function with no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single parameter, existing output schema, and annotations covering safety, the description fully covers the tool's functionality, including what data is returned and its official nature.

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 coverage is 100% with a clear description of the 'slug' parameter referencing list_cities. The description does not add new parameter details beyond the schema, so a baseline of 3 is appropriate.

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?

The description explicitly states 'Get official air quality for a German city (PM10, NO2 and more),' specifying the verb, resource, and scope. It differentiates from sibling tools by mentioning an alternative for live readings.

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

Usage Guidelines5/5

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

The description provides explicit when-not-to-use guidance: 'For live nearest-station hourly readings use get_city_resource(slug, resource='air') instead,' and names the alternative tool.

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

Deploy Server