Skip to main content
Glama

Airnow

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Current By Location

current_by_location
Read-onlyIdempotent

Latest observed AQI for the AirNow station nearest a lat/lon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesUS latitude
longitudeYesUS longitude
distance_milesNoSearch radius (default 25, max 250)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of observations returned
latitudeYesQuery latitude
longitudeYesQuery longitude
observationsYesLatest AQI observations for nearest station

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "distance_miles": 100,
+    "latitude": 34.0522,
+    "longitude": -118.2437
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of observations returned",
+      "type": "integer"
+    },
+    "latitude": {
+      "description": "Query latitude",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Query longitude",
+      "type": "number"
+    },
+    "observations": {
+      "description": "Latest AQI observations for nearest station",
+      "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"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude",
+    "count",
+    "observations"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds 'latest observed' and 'nearest station' but does not disclose edge cases like missing stations or single-result limitation. With annotations present, the description provides adequate but not extra context.

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?

A single clear sentence with no redundancy. Every word adds value and the purpose is immediately understood.

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 tool's simplicity, the presence of annotations, a complete input schema, and an output schema, the description is sufficiently complete. It succinctly describes the core function without needing further detail.

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%, so all parameters are documented in the schema. The description does not add additional semantics beyond what the schema already provides. 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?

Description clearly states the tool returns the latest AQI for the nearest AirNow station given lat/lon coordinates. This differentiates it from the sibling tool 'current_by_zip' which uses a ZIP code.

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 latitude and longitude are available, but does not explicitly state when to use this tool over alternatives like 'current_by_zip' or mention any exclusions. Guidance is minimal but not misleading.

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