Skip to main content
Glama

Openaq

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Air Quality Near

air_quality_near
Read-onlyIdempotent

Get the latest air-quality readings (PM2.5, PM10, O3, NO2, SO2, CO, etc.) at the monitoring station NEAREST to a latitude/longitude. PREFER for "air quality near me", "what is the air quality at ", "is the air bad in right now". Returns the nearest station with its most recent pollutant values, plus other nearby stations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyNoOpenAQ API key (optional; the gateway supplies one).
latitudeYesLatitude in decimal degrees (e.g., 40.785).
longitudeYesLongitude in decimal degrees (e.g., -73.968).
radius_kmNoSearch radius in km (default 12, max 25 — OpenAQ limit).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.785,
+    "longitude": -73.968
+  },
+  {
+    "latitude": 28.6139,
+    "longitude": 77.209,
+    "radius_km": 15
+  }
+]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint) already indicate safe, non-destructive behavior. The description adds valuable context: it returns the nearest station with most recent pollutant values and other nearby stations, going beyond what annotations provide. No contradiction.

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 main action, then usage examples, then what it returns. No unnecessary words; every sentence adds value. Structure is efficient and easy to parse.

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 4 parameters (all documented in schema), complete annotations, and no output schema, the description adequately explains what the tool returns (nearest station values and nearby stations). No gaps identified.

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% (all parameters have descriptions). The tool description does not add meaning beyond the schema, such as format or constraints. Per guidelines, baseline 3 is appropriate when schema fully covers parameters.

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 the latest air-quality readings... at the monitoring station NEAREST to a latitude/longitude.' It specifies the pollutants and indicates it returns multiple stations, making the purpose unambiguous and distinct from sibling tools.

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 explicit usage contexts like 'air quality near me', 'what is the air quality at <coordinates>', and 'is the air bad in <place> right now', guiding when to prefer this tool. It does not explicitly exclude alternative tools but the guidance is clear and sufficient.

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

All Openaq 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.

Resources