Skip to main content
Glama

Airnow

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Observations In Bbox

observations_in_bbox
Read-onlyIdempotent

Historical AQI observations inside a bounding box for a date range. Specify pollutants as comma-separated parameter codes (e.g., "OZONE,PM25,PM10,CO,NO2,SO2"). bbox format: "minLon,minLat,maxLon,maxLat".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxYesminLon,minLat,maxLon,maxLat
verboseNoInclude site / county / agency / full-AQS-code fields
end_dateYesYYYY-MM-DDT23
data_typeNoA (AQI) | C (concentration) | B (both, default)
parametersNoComma-separated pollutants (default: OZONE,PM25,PM10)
start_dateYesYYYY-MM-DDT00 (hour-granular ISO truncated)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxYesBounding box queried (minLon,minLat,maxLon,maxLat)
countYesNumber of observations returned
observationsYesHistorical AQI observations in bounding box

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "bbox": "-74.1,40.6,-73.9,40.8",
+    "end_date": "2025-01-10T23",
+    "start_date": "2025-01-10T00"
+  },
+  {
+    "bbox": "-118.3,34.0,-118.2,34.1",
+    "data_type": "A",
+    "end_date": "2025-01-10T23",
+    "parameters": "OZONE,PM25,NO2",
+    "start_date": "2025-01-08T00",
+    "verbose": true
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "bbox": {
+      "description": "Bounding box queried (minLon,minLat,maxLon,maxLat)",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of observations returned",
+      "type": "integer"
+    },
+    "observations": {
+      "description": "Historical AQI observations in bounding box",
+      "items": {
+        "properties": {
+          "agency": {
+            "description": "Reporting agency name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "aqi": {
+            "description": "Air Quality Index value",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "aqs_code": {
+            "description": "Full AQS code identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category": {
+            "description": "AQI category numeric code",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "hour": {
+            "description": "Hour observed (0-23)",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Site latitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Site longitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "observed_date": {
+            "description": "Date observed (YYYY-MM-DD)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pollutant": {
+            "description": "Pollutant parameter name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "site": {
+            "description": "Monitoring site name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "unit": {
+            "description": "Unit of measurement",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "utc": {
+            "description": "UTC timestamp",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "value": {
+            "description": "Pollutant concentration value",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "bbox",
+    "count",
+    "observations"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds minimal behavioral context beyond the annotations, such as the bbox format and pollutant specification. It does not discuss pagination, rate limits, or data sparsity.

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 long, front-loaded with the primary purpose, and contains no superfluous information. Every sentence earns its place.

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?

Given full schema coverage, annotations, and an output schema, the description covers the essential usage context. It could mention time granularity (hourly) or that results may include multiple sites, but the output schema likely clarifies this.

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%, and the schema includes descriptions for all parameters. The description adds an example of pollutant codes but does not provide additional meaning beyond what the schema already conveys.

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 states it returns 'Historical AQI observations inside a bounding box for a date range,' which is a specific verb+resource combination. It clearly distinguishes itself from sibling tools that focus on current or forecast data, such as current_by_location or forecast_by_zip.

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 for historical AQI queries but does not explicitly state when to use this tool versus alternatives like current_by_location. There is no mention of caveats, limitations, or contraindications.

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