Skip to main content
Glama

Airnow

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Current By Location

current_by_location
Read-onlyIdempotent

Latest observed air quality index (AQI) for the EPA AirNow reporting area nearest a latitude/longitude in the US: one row per pollutant with AQI value, category, observation hour, agency and yesterday's AQI. Answers "what is the air quality at these coordinates right now".

Input Schema

NameRequiredDescriptionDefault
latitudeYesUS latitude
longitudeYesUS longitude
distance_milesNoSearch radius for the nearest reporting area (default 25, max 250)

Output 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. Changed1 schema field changed
    • changedInput schema / properties / distance_miles / description
      Previous value: -"Search radius (default 25, max 250)"New value: +"Search radius for the nearest reporting area (default 25, max 250)"
  2. 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"
+}
  3. 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 readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real context beyond that: the upstream source (EPA AirNow), the one-row-per-pollutant granularity, the fields returned including observation hour and yesterday's AQI, and a US-only geographic constraint. It does not say what happens when no reporting area falls within the radius, which is the remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the resource and scope, followed by a short user-intent quote. The field enumeration is slightly list-heavy but each item carries information. No filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and rich annotations, the description need not explain return values, and it correctly focuses on source, granularity and geographic restriction. The main omission is the empty-result behavior (no reporting area within distance_miles), which an agent would want before calling.

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 coverage is 100%, with latitude/longitude and distance_miles (default 25, max 250) fully documented in the schema. The description's phrase 'nearest a latitude/longitude' reinforces the role of distance_miles but adds no new syntax or meaning, so the baseline of 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?

States a concrete verb and resource ('Latest observed air quality index (AQI)') and pins the scope to the EPA AirNow reporting area nearest a latitude/longitude in the US, with one row per pollutant. This cleanly separates it from the ZIP-based sibling current_by_zip without even needing to name it.

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?

Gives clear usage context: use it when you have coordinates and want current air quality ('what is the air quality at these coordinates right now'), and it restricts input to US locations. It stops short of explicitly naming current_by_zip as the alternative when the user has a ZIP rather than coordinates, so no exclusion rule is stated.

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