Skip to main content
Glama

science

by io.github.pipeworx-io
OverviewAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude in decimal degrees, e.g. 40.7128. Required — this tool does not geocode city names.
longitudeYesLongitude in decimal degrees, e.g. -74.006.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stationsYesAir quality monitoring stations near coordinates

Schema Changelog

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

  1. Changed2 schema fields changed
    • 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."
  2. Changed2 schema fields changed
    • 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"
+}
  3. Changed2 schema fields changed
    • 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
  4. Changed1 schema field changed
    • 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"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "latitude": 34.0522,
+    "longitude": -118.2437
+  }
+]
  6. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds context about what data is returned (US AQI, pollutants), but no additional behavioral traits such as rate limits, authentication, or limitations beyond what the schema states. No contradiction with 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 a single, front-loaded sentence that states the action, resource, and return values without any fluff or repetition. Every word earns its place.

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?

The tool is simple, with annotations covering safety, an output schema covering return structure, and schema descriptions covering parameters. The description effectively covers the purpose and key outputs, making it complete for its 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 both latitude and longitude fully described and examples provided. The description only says 'at a latitude/longitude', which adds no extra meaning beyond what the schema already provides. Baseline 3 applies.

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 uses a specific verb 'check' with resource 'air quality' and specifies the coordinate parameters. It clearly distinguishes from siblings by its unique domain, and the list of return values adds specificity.

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 provides clear context on when to use the tool (when you need current air quality at a latitude/longitude), but it does not explicitly mention alternatives or when not to use it. The schema adds 'does not geocode city names', which is a usage exclusion, but that is not in the description itself.

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

All science toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources