Skip to main content
Glama

Airnow

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Current By Zip

current_by_zip
Read-onlyIdempotent

Latest observed AQI for a US ZIP code. Returns one record per pollutant reported at the nearest site (typically O3 + PM2.5). Includes AQI value, category (Good / Moderate / etc.), reporting area, and timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zip_codeYesUS 5-digit ZIP code
distance_milesNoSearch radius (default 25, max 250)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of observations returned
zip_codeYesUS 5-digit ZIP code queried
observationsYesLatest AQI observations for pollutants at nearest site

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "zip_code": "10001"
+  },
+  {
+    "distance_miles": 50,
+    "zip_code": "90210"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of observations returned",
+      "type": "integer"
+    },
+    "observations": {
+      "description": "Latest AQI observations for pollutants at nearest site",
+      "items": {
+        "properties": {
+          "aqi": {
+            "description": "Air Quality Index value",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "category": {
+            "description": "AQI category (Good, Moderate, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category_number": {
+            "description": "AQI category numeric code",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "Date observed (YYYY-MM-DD)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "hour": {
+            "description": "Hour observed (0-23)",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Site latitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Site longitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "pollutant": {
+            "description": "Pollutant name (e.g., O3, PM2.5)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reporting_area": {
+            "description": "Geographic area name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "State code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "timezone": {
+            "description": "Local time zone",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "zip_code": {
+      "description": "US 5-digit ZIP code queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "zip_code",
+    "count",
+    "observations"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds behavioral specifics: returns one record per pollutant, uses nearest site, includes category and timestamp. This context goes beyond the annotations without contradicting them.

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 sentences convey the core purpose, return structure, and typical behavior. No extraneous content; front-loaded with the primary action. Highly efficient.

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?

Given the output schema exists (context signal) and annotations provide safety profile, the description is complete for a simple read tool. It explains what data is returned and the geographical resolution (nearest site). No obvious gaps.

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 covers 100% of parameters with descriptions for zip_code and distance_miles. The description does not add new parameter information, so it relies on the schema. Baseline 3 is appropriate.

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 returns the latest observed AQI for a US ZIP code, specifying it returns one record per pollutant (typically O3 and PM2.5) with AQI value, category, area, and timestamp. This distinguishes it from sibling tools like current_by_location (which uses lat/lng) and forecast_by_zip (forecast).

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 implicitly defines usage: querying current AQI by ZIP. However, it does not explicitly state when to use this tool versus alternatives like current_by_location or forecast_by_zip, nor does it mention exclusions (e.g., non-US ZIPs). Sibling tools are listed in context but not referenced in the description.

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

All Airnow toolsInspect
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.

Resources