Skip to main content
Glama

airquality

by io.github.pipeworx-io

Get Forecast

get_forecast
Read-onlyIdempotent

Get hourly air quality forecast for a location. Returns US AQI, PM2.5, and PM10 predictions. Use to plan activities or alert users to upcoming poor air conditions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of forecast days (1-7, default 3).
latitudeYesLatitude of the location.
longitudeYesLongitude of the location.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursYesHourly air quality forecast
latitudeYesLatitude of the location
longitudeYesLongitude of the location

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: +[
+  {
+    "days": 3,
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "days": 5,
+    "latitude": 37.7749,
+    "longitude": -122.4194
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "hours": {
+      "description": "Hourly air quality forecast",
+      "items": {
+        "properties": {
+          "aqi_category": {
+            "description": "AQI category (Good, Moderate, Unhealthy, etc.)",
+            "type": "string"
+          },
+          "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"
+          },
+          "time": {
+            "description": "ISO 8601 timestamp for the forecast hour",
+            "type": "string"
+          },
+          "us_aqi": {
+            "description": "US Air Quality Index score",
+            "type": "number"
+          }
+        },
+        "required": [
+          "time",
+          "us_aqi",
+          "aqi_category",
+          "pm2_5_ug_m3",
+          "pm10_ug_m3"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "latitude": {
+      "description": "Latitude of the location",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Longitude of the location",
+      "type": "number"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude",
+    "hours"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "lat": 37.7749,
-    "lon": -122.4194
-  },
-  {
-    "lat": 40.7128,
-    "lon": -74.006
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "location": {
-      "properties": {
-        "city": {
-          "description": "City name of the location",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "lat": {
-          "description": "Latitude of the location",
-          "type": "number"
-        },
-        "lon": {
-          "description": "Longitude of the location",
-          "type": "number"
-        },
-        "state": {
-          "description": "State of the location",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "lat",
-        "lon",
-        "city",
-        "state"
-      ],
-      "type": "object"
-    },
-    "periods": {
-      "items": {
-        "properties": {
-          "detailed_forecast": {
-            "description": "Detailed forecast description",
-            "type": "string"
-          },
-          "end_time": {
-            "description": "ISO 8601 end time of the period",
-            "type": "string"
-          },
-          "is_daytime": {
-            "description": "Whether the period is during daytime",
-            "type": "boolean"
-          },
-          "name": {
-            "description": "Period name (e.g., 'Tonight', 'Tuesday')",
-            "type": "string"
-          },
-          "short_forecast": {
-            "description": "Brief forecast description",
-            "type": "string"
-          },
-          "start_time": {
-            "description": "ISO 8601 start time of the period",
-            "type": "string"
-          },
-          "temperature": {
-            "description": "Temperature value",
-            "type": "number"
-          },
-          "temperature_unit": {
-            "description": "Temperature unit (F or C)",
-            "type": "string"
-          },
-          "wind_direction": {
-            "description": "Wind direction (e.g., 'N', 'SW')",
-            "type": "string"
-          },
-          "wind_speed": {
-            "description": "Wind speed description",
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "start_time",
-          "end_time",
-          "is_daytime",
-          "temperature",
-          "temperature_unit",
-          "wind_speed",
-          "wind_direction",
-          "short_forecast",
-          "detailed_forecast"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "location",
-    "periods"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "location": {
+      "properties": {
+        "city": {
+          "description": "City name of the location",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "lat": {
+          "description": "Latitude of the location",
+          "type": "number"
+        },
+        "lon": {
+          "description": "Longitude of the location",
+          "type": "number"
+        },
+        "state": {
+          "description": "State of the location",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "lat",
+        "lon",
+        "city",
+        "state"
+      ],
+      "type": "object"
+    },
+    "periods": {
+      "items": {
+        "properties": {
+          "detailed_forecast": {
+            "description": "Detailed forecast description",
+            "type": "string"
+          },
+          "end_time": {
+            "description": "ISO 8601 end time of the period",
+            "type": "string"
+          },
+          "is_daytime": {
+            "description": "Whether the period is during daytime",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Period name (e.g., 'Tonight', 'Tuesday')",
+            "type": "string"
+          },
+          "short_forecast": {
+            "description": "Brief forecast description",
+            "type": "string"
+          },
+          "start_time": {
+            "description": "ISO 8601 start time of the period",
+            "type": "string"
+          },
+          "temperature": {
+            "description": "Temperature value",
+            "type": "number"
+          },
+          "temperature_unit": {
+            "description": "Temperature unit (F or C)",
+            "type": "string"
+          },
+          "wind_direction": {
+            "description": "Wind direction (e.g., 'N', 'SW')",
+            "type": "string"
+          },
+          "wind_speed": {
+            "description": "Wind speed description",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "start_time",
+          "end_time",
+          "is_daytime",
+          "temperature",
+          "temperature_unit",
+          "wind_speed",
+          "wind_direction",
+          "short_forecast",
+          "detailed_forecast"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "location",
+    "periods"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lat": 37.7749,
+    "lon": -122.4194
+  },
+  {
+    "lat": 40.7128,
+    "lon": -74.006
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by specifying the return content (hourly predictions, US AQI, PM2.5, PM10) and the temporal nature of the data, without contradicting 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 two sentences, front-loaded with the core action and return data, followed by a concise use case. Every sentence earns its place with no unnecessary detail.

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?

For a simple read-only forecast tool with full schema coverage, comprehensive annotations, and an output schema, the description adequately covers purpose, return values, and usage context. No critical information is missing for an agent to select and invoke this tool correctly.

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 provides 100% description coverage for all three parameters (latitude, longitude, days), so the schema already documents parameter semantics. The description does not add any additional parameter details beyond what the schema provides, which meets the baseline for full coverage.

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 tool's function: 'Get hourly air quality forecast for a location' and specifies the returned data (US AQI, PM2.5, PM10). This distinguishes it from the sibling get_air_quality tool, which likely provides current conditions rather than a forecast.

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 usage scenarios: 'Use to plan activities or alert users to upcoming poor air conditions.' While it does not explicitly mention alternatives like get_air_quality, the forecast context and focus on upcoming conditions effectively signal when this tool is appropriate.

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