Skip to main content
Glama

airquality

by io.github.pipeworx-io

Get Air Quality

get_air_quality
Read-onlyIdempotent

Check current air quality at a location (latitude/longitude or city name, e.g., "40.7128, -74.0060" or "New York"). Returns US AQI score, PM2.5, PM10, CO, NO2, and ozone levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location.
longitudeYesLongitude of the location.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
us_aqiYesUS Air Quality Index score
latitudeYesLatitude of the location
longitudeYesLongitude of the location
pm10_ug_m3YesPM10 concentration in micrograms per cubic meter
ozone_ug_m3YesOzone concentration in micrograms per cubic meter
pm2_5_ug_m3YesPM2.5 concentration in micrograms per cubic meter
aqi_categoryYesAQI category (Good, Moderate, Unhealthy, etc.)
carbon_monoxide_ug_m3YesCarbon monoxide concentration in micrograms per cubic meter
nitrogen_dioxide_ug_m3YesNitrogen dioxide concentration in micrograms per cubic meter

Schema Changelog

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

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

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds value by specifying the return payload (AQI, PM2.5, etc.) and noting that the data is 'current', which is not present in annotations. No contradictions exist.

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 concise, front-loading the action and purpose in the first sentence. It provides examples and return values in a compact two-sentence structure without unnecessary fluff. This is exemplary conciseness.

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?

Though a rich output schema exists, the description adds useful operational context like 'current' and 'US AQI'. The critical gap is the unsupported city-name input, which creates a completeness issue. For a simple tool, the description is mostly sufficient but not fully reliable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides 100% coverage with brief descriptions for latitude and longitude, so the baseline is 3. However, the description actively misleadingly claims city names are accepted, while the schema requires numeric lat/long. This undermines parameter clarity, so a lower score is warranted.

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' and resource 'air quality', clearly distinguishing it from sibling tools like get_forecast. It also lists the exact pollutants returned, reinforcing the purpose. The mention of alternate location formats does not obscure the core purpose.

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

Usage Guidelines3/5

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

The description implies usage when current air quality is needed, but it does not explicitly reference alternatives or exclusions. No when-not conditions are stated. The misleading city name suggestion could lead to incorrect usage, though this is more of a parameter issue.

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

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

TDQS

A3.5/5.0
Disambiguation3/5

Many tools have overlapping purposes, especially multiple ask_pipeworx variants and numerous Polymarket tools. Detailed descriptions help, but an agent could still confuse similar tools like ask_pipeworx and ask_pipeworx_beta.

Naming Consistency2/5

Tool names use a mix of styles: some are descriptive (get_air_quality), some use proprietary prefixes (pipeworx_feedback), and others are arbitrary (bet_research). No consistent verb_noun pattern.

Tool Count1/5

33 tools is excessive for a server named 'airquality', which only has 2 air-quality-specific tools. The count is appropriate for a general data platform, but mismatched with the server name.

Completeness1/5

For the air quality domain, the tool set is severely incomplete, missing historical data, pollution sources, and health recommendations. The overall set covers many other domains, but fails to address the server's apparent focus.

Resources