Skip to main content
Glama
malkreide

Zurich Open Data MCP Server

by malkreide
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

zurich_air_quality

Read-only

Get current air quality measurements from Zurich's monitoring stations. Filter by station and pollutant to see live NO2, O3, PM10, and more values with units.

Instructions

Liefert stündlich aktualisierte Luftqualitätsmessungen aus Zürich.

Datenquelle: Umwelt- und Gesundheitsschutz Stadt Zürich (UGZ). Parameter: NO, NO2, NOx, O3, PM10, PM2.5.

Returns: Aktuelle Schadstoffwerte je Station mit Einheiten

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / $defs / AirQualityInput / properties / format
      Added value: +{
+  "default": "markdown",
+  "description": "Ausgabeformat: 'markdown' (Standard, lesbar) oder 'json' (maschinenlesbar).",
+  "enum": [
+    "markdown",
+    "json"
+  ],
+  "title": "Format",
+  "type": "string"
+}
    • changedInput schema / $defs / AirQualityInput / properties / parameter / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "NO",
+      "NO2",
+      "NOx",
+      "O3",
+      "PM10",
+      "PM2.5"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / AirQualityInput / properties / parameter / description
      Previous value: -"Schadstoff: 'NO2' (Stickstoffdioxid), 'O3' (Ozon), 'PM10' (Feinstaub), 'PM2.5', 'NOx', 'SO2', 'CO'. Leer = alle."New value: +"Schadstoff: 'NO2' (Stickstoffdioxid), 'O3' (Ozon), 'PM10' (Feinstaub), 'PM2.5', 'NO', 'NOx'. Leer = alle."
    • changedInput schema / $defs / AirQualityInput / properties / station / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "Zch_Heubeeribüel",
+      "Zch_Rosengartenstrasse",
+      "Zch_Schimmelstrasse",
+      "Zch_Stampfenbachstrasse"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / AirQualityInput / properties / station / description
      Previous value: -"Messstation: 'Zch_Stampfenbachstrasse', 'Zch_Schimmelstrasse', 'Zch_Rosengartenstrasse', 'Zch_Heubeeribüel', 'Zch_Kaserne'. Leer = alle."New value: +"Messstation filtern. Verfügbar: Zch_Heubeeribüel, Zch_Rosengartenstrasse, Zch_Schimmelstrasse, Zch_Stampfenbachstrasse. Leer = alle."
  2. First observedv0.3.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds value by specifying the data source (UGZ), update frequency (hourly), and that it returns current values per station with units. This provides operational context beyond the annotations.

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 extremely concise: three sentences covering purpose, data source, and return format. Every sentence adds value, and the most important information is front-loaded.

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 a simple read-only query tool with well-documented parameters and annotations, the description is adequate. However, it lacks usage guidelines and does not explain the output schema (which exists but is not shown). This leaves minor gaps in completeness.

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 input schema already provides detailed descriptions for all parameters (limit, format, station, parameter) with enums and defaults. The tool description only lists the parameters generically, adding no extra meaning. Since schema coverage is high, baseline 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 clearly states the verb (liefert), resource (Luftqualitätsmessungen aus Zürich), and update frequency (stündlich). It also lists the measured parameters. This sufficiently distinguishes it from sibling tools which focus on other datasets like parking or weather.

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 is provided on when to use this tool versus alternatives, or any conditions/precautions. The description does not mention when not to use it or suggest other tools for related queries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/zurich-opendata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server