Waqi

Get Aqi By Station

get_aqi_by_station

Read-onlyIdempotent

Real-time AQI for a specific WAQI station by UID (numeric).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`station_id`	Yes	WAQI station UID (returned by search_stations)

Output Schema

TableJSON Schema

Name	Required	Description
`aqi`	Yes	Air Quality Index value
`station`	Yes
`category`	Yes	AQI category (Good/Moderate/Unhealthy/Hazardous)
`timezone`	Yes	Timezone of station
`measured_at`	Yes	ISO timestamp of measurement
`attributions`	Yes	Data sources and attributions
`measurements`	Yes
`dominant_pollutant`	Yes	Primary pollutant causing poor air quality

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "station_id": 7530
+  },
+  {
+    "station_id": 12891
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "aqi": {
+      "description": "Air Quality Index value",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "attributions": {
+      "description": "Data sources and attributions",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Attribution source name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Attribution source URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "category": {
+      "description": "AQI category (Good/Moderate/Unhealthy/Hazardous)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dominant_pollutant": {
+      "description": "Primary pollutant causing poor air quality",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "measured_at": {
+      "description": "ISO timestamp of measurement",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "measurements": {
+      "properties": {
+        "co": {
+          "description": "Carbon monoxide in µg/m³",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "humidity_pct": {
+          "description": "Humidity percentage",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "no2": {
+          "description": "Nitrogen dioxide in µg/m³",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "o3": {
+          "description": "Ozone concentration in µg/m³",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pm10": {
+          "description": "PM10 concentration in µg/m³",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pm25": {
+          "description": "PM2.5 concentration in µg/m³",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pressure_hpa": {
+          "description": "Atmospheric pressure in hPa",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "so2": {
+          "description": "Sulfur dioxide in µg/m³",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "temperature_c": {
+          "description": "Temperature in Celsius",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "wind_speed": {
+          "description": "Wind speed",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "station": {
+      "properties": {
+        "id": {
+          "description": "Station identifier",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "latitude": {
+          "description": "Station latitude",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "longitude": {
+          "description": "Station longitude",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Station/city name",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Station information URL",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "timezone": {
+      "description": "Timezone of station",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "aqi",
+    "category",
+    "dominant_pollutant",
+    "station",
+    "measurements",
+    "measured_at",
+    "timezone",
+    "attributions"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive traits. The description adds value by disclosing 'Real-time' behavior (data may change) and the external source 'WAQI', which are not present in annotations. No contradiction found.

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 a single, front-loaded sentence that conveys purpose, scope, and selection method. Every word earns its place with no redundancy or filler.

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 simple one-parameter read-only tool with a complete output schema and rich annotations, the description is quite sufficient. It could optionally mention the need for prior search_stations, but that is already in the parameter description. Overall, the context is complete for the tool's complexity.

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%, with the parameter description already explaining 'WAQI station UID (returned by search_stations)'. The tool description adds only 'numeric', which is already captured by the schema type 'number'. Thus, the description does not significantly enrich parameter meaning.

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 'Real-time AQI for a specific WAQI station by UID (numeric)' clearly states the action (get AQI), the resource (specific station), and the selection method (numeric UID). It distinguishes from siblings like get_aqi_by_city and get_aqi_by_location by emphasizing station UID.

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

Usage Guidelines4/5

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

The description implies when to use this tool (when you have a station UID) and the parameter description explicitly states the UID is returned by search_stations, providing a clear prerequisite. However, it does not explicitly name alternative tools or state when not to use it.

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

All Waqi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.