Science

Get Air Quality

get_air_quality

Read-onlyIdempotent

Check current air quality at a latitude/longitude. Returns US AQI score and category plus PM2.5, PM10, ozone, NO2, and CO levels.

Input Schema

Name	Required	Description	Default
`latitude`	Yes	Latitude in decimal degrees, e.g. 40.7128. Required — this tool does not geocode city names.
`longitude`	Yes	Longitude in decimal degrees, e.g. -74.006.

Output Schema

Name	Required	Description	Default
`pm10`	No
`ozone`	No
`pm2_5`	No
`units`	No
`source`	No
`us_aqi`	No
`latitude`	No
`longitude`	No
`observed_at`	No
`aqi_category`	No
`carbon_monoxide`	No
`nitrogen_dioxide`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 5, 2026

addedOutput schema / properties / aqi_category
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / carbon_monoxide
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / latitude
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / longitude
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / nitrogen_dioxide
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / observed_at
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ozone
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / pm10
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / pm2_5
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / source
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / stations

Removed value: -{
-  "description": "Air quality monitoring stations near coordinates",
-  "items": {
-    "properties": {
-      "city": {
-        "description": "City name",
-        "type": "string"
-      },
-      "country": {
-        "description": "Country name",
-        "type": "string"
-      },
-      "location": {
-        "description": "Station location name",
-        "type": "string"
-      },
-      "measurements": {
-        "description": "Air quality measurements",
-        "items": {
-          "properties": {
-            "last_updated": {
-              "description": "ISO 8601 timestamp of last update",
-              "type": "string"
-            },
-            "parameter": {
-              "description": "Measured parameter (e.g., PM2.5, PM10)",
-              "type": "string"
-            },
-            "unit": {
-              "description": "Unit of measurement",
-              "type": "string"
-            },
-            "value": {
-              "description": "Measurement value",
-              "type": "number"
-            }
-          },
-          "required": [
-            "parameter",
-            "value",
-            "unit",
-            "last_updated"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "location",
-      "city",
-      "country",
-      "measurements"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / units

Added value: +{
+  "properties": {
+    "carbon_monoxide": {
+      "type": "string"
+    },
+    "interval": {
+      "type": "string"
+    },
+    "nitrogen_dioxide": {
+      "type": "string"
+    },
+    "ozone": {
+      "type": "string"
+    },
+    "pm10": {
+      "type": "string"
+    },
+    "pm2_5": {
+      "type": "string"
+    },
+    "time": {
+      "type": "string"
+    },
+    "us_aqi": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / us_aqi
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / required
```
Removed value: -[
-  "stations"
-]
```

Changed2 schema fields changedJul 30, 2026

changedInput schema / properties / latitude / description

Previous value: -"Latitude"New value: +"Latitude in decimal degrees, e.g. 40.7128. Required — this tool does not geocode city names."

changedInput schema / properties / longitude / description

Previous value: -"Longitude"New value: +"Longitude in decimal degrees, e.g. -74.006."

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "latitude": 51.5074,
+    "longitude": -0.1278
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "stations": {
+      "description": "Air quality monitoring stations near coordinates",
+      "items": {
+        "properties": {
+          "city": {
+            "description": "City name",
+            "type": "string"
+          },
+          "country": {
+            "description": "Country name",
+            "type": "string"
+          },
+          "location": {
+            "description": "Station location name",
+            "type": "string"
+          },
+          "measurements": {
+            "description": "Air quality measurements",
+            "items": {
+              "properties": {
+                "last_updated": {
+                  "description": "ISO 8601 timestamp of last update",
+                  "type": "string"
+                },
+                "parameter": {
+                  "description": "Measured parameter (e.g., PM2.5, PM10)",
+                  "type": "string"
+                },
+                "unit": {
+                  "description": "Unit of measurement",
+                  "type": "string"
+                },
+                "value": {
+                  "description": "Measurement value",
+                  "type": "number"
+                }
+              },
+              "required": [
+                "parameter",
+                "value",
+                "unit",
+                "last_updated"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "location",
+          "city",
+          "country",
+          "measurements"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "stations"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "latitude": 40.7128,
-    "longitude": -74.006
-  },
-  {
-    "latitude": 34.0522,
-    "longitude": -118.2437
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "aqi_category": {
-      "description": "AQI category (Good, Moderate, Unhealthy, etc.)",
-      "type": "string"
-    },
-    "carbon_monoxide_ug_m3": {
-      "description": "Carbon monoxide concentration in micrograms per cubic meter",
-      "type": "number"
-    },
-    "latitude": {
-      "description": "Latitude of the location",
-      "type": "number"
-    },
-    "longitude": {
-      "description": "Longitude of the location",
-      "type": "number"
-    },
-    "nitrogen_dioxide_ug_m3": {
-      "description": "Nitrogen dioxide concentration in micrograms per cubic meter",
-      "type": "number"
-    },
-    "ozone_ug_m3": {
-      "description": "Ozone concentration in micrograms per cubic meter",
-      "type": "number"
-    },
-    "pm10_ug_m3": {
-      "description": "PM10 concentration in micrograms per cubic meter",
-      "type": "number"
-    },
-    "pm2_5_ug_m3": {
-      "description": "PM2.5 concentration in micrograms per cubic meter",
-      "type": "number"
-    },
-    "us_aqi": {
-      "description": "US Air Quality Index score",
-      "type": "number"
-    }
-  },
-  "required": [
-    "latitude",
-    "longitude",
-    "us_aqi",
-    "aqi_category",
-    "pm2_5_ug_m3",
-    "pm10_ug_m3",
-    "carbon_monoxide_ug_m3",
-    "nitrogen_dioxide_ug_m3",
-    "ozone_ug_m3"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "aqi_category": {
+      "description": "AQI category (Good, Moderate, Unhealthy, etc.)",
+      "type": "string"
+    },
+    "carbon_monoxide_ug_m3": {
+      "description": "Carbon monoxide concentration in micrograms per cubic meter",
+      "type": "number"
+    },
+    "latitude": {
+      "description": "Latitude of the location",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Longitude of the location",
+      "type": "number"
+    },
+    "nitrogen_dioxide_ug_m3": {
+      "description": "Nitrogen dioxide concentration in micrograms per cubic meter",
+      "type": "number"
+    },
+    "ozone_ug_m3": {
+      "description": "Ozone concentration in micrograms per cubic meter",
+      "type": "number"
+    },
+    "pm10_ug_m3": {
+      "description": "PM10 concentration in micrograms per cubic meter",
+      "type": "number"
+    },
+    "pm2_5_ug_m3": {
+      "description": "PM2.5 concentration in micrograms per cubic meter",
+      "type": "number"
+    },
+    "us_aqi": {
+      "description": "US Air Quality Index score",
+      "type": "number"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude",
+    "us_aqi",
+    "aqi_category",
+    "pm2_5_ug_m3",
+    "pm10_ug_m3",
+    "carbon_monoxide_ug_m3",
+    "nitrogen_dioxide_ug_m3",
+    "ozone_ug_m3"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "latitude": 34.0522,
+    "longitude": -118.2437
+  }
+]

First observedApr 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=true and non-destructive, so the safe-read profile is fully covered by structured data. The description adds the 'current' temporal scope and enumerates returned pollutants, which is mild added context, but says nothing about rate limits, data freshness/latency, or error behavior for invalid coordinates.

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?

Two tight sentences: the first states the action and input, the second states the return payload. No filler, no repetition of the title, and the core capability 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?

With an output schema present, the description need not detail return values, and it correctly summarizes the AQI score plus pollutant levels instead. Annotations and schema cover safety and parameters, so only explicit usage guidance is missing.

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% and the schema already documents both parameters, including the explicit 'does not geocode city names' constraint. The description restates the lat/long requirement without adding format, range, or precision guidance beyond the schema, so baseline 3 applies.

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 and resource ('Check current air quality') and names the required input (latitude/longitude), plus the headline output (US AQI). It does not differentiate itself from nearby sibling tools such as get_earthquakes or get_iss_location, but the purpose itself is unambiguous.

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?

The word 'current' implies a real-time-only scope, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent gets no help deciding between this and other location-based data tools.

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

All Science 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.

Get Air Quality

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources