EPA Air Quality & Toxics

get_current_aqi

Get the current Air Quality Index (AQI) for a location.

Provide either a zip_code OR latitude/longitude coordinates.
Returns AQI values, pollutant levels, and health category for
each measured pollutant at the nearest monitoring station.

Args:
    zip_code: US ZIP code (e.g. '20001').
    latitude: Latitude of the location (e.g. 38.9).
    longitude: Longitude of the location (e.g. -77.0).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`latitude`	No
`zip_code`	No
`longitude`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool uses the 'nearest monitoring station' and returns pollutant-specific data, which is useful context beyond the simple 'Get' verb. It could be more explicit about being read-only, but the name and verb make that obvious.

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 concise and front-loaded with the core purpose. The Args section is cleanly structured and every sentence adds value. No unnecessary words or repetition.

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?

The description covers the essential aspects for a simple lookup tool: input constraints, algorithm (nearest station), and what is returned. The output schema exists, so detailed return structure is handled elsewhere. Minor gaps like error cases or exact output schema references are not critical for using the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no parameter descriptions (0% coverage), but the `Args` section thoroughly explains each parameter with format examples (e.g., '20001', 38.9) and clarifies the mutual exclusivity of zip_code versus latitude/longitude. This fully compensates for the schema's lack of detail.

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 a specific verb and resource: 'Get the current Air Quality Index (AQI) for a location.' The word 'current' clearly distinguishes this from siblings like get_aqi_forecast and get_annual_air_quality. It also specifies what is returned (AQI values, pollutant levels, health category).

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?

Provides clear guidance on parameter usage by stating 'Provide either a zip_code OR latitude/longitude coordinates,' which is important for correct invocation. However, it does not explicitly compare with alternative tools (e.g., forecast or annual), though the 'current' context implies when to use this versus siblings.

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

All EPA Air Quality & Toxics tools Inspect

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.

TDQS

A4.5/5.0

Disambiguation4/5

The two air quality tools (current and forecast) are clearly separated by time frame, and the historical summary is distinct. The two toxics tools (Superfund and TRI) are both state-based hazard listings but differ in content (cleanup sites vs. reporting facilities). Minor potential confusion between Superfund and TRI, but descriptions clarify.

Naming Consistency5/5

All tools use the consistent 'get_' prefix followed by descriptive noun phrases in snake_case. The pattern is uniform across the set.

Tool Count5/5

Five tools cover the server's stated scope of air quality and toxics without redundancy. Each tool addresses a distinct data need, and the count is within the ideal 3-15 range.

Completeness4/5

The air quality surface covers current, forecast, and annual historical data. The toxics surface covers site and facility listings. Missing are detailed facility-level emissions or site-specific cleanup data, but core queries are supported.

Resources

Need Help?