Toxics Release Inventory, Superfund sites, air quality data, and AQI
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4/5 across 5 of 5 tools scored.
Each tool has a clearly distinct purpose with no overlap: annual air quality summaries, AQI forecasts, current AQI readings, Superfund sites, and TRI facilities. The tools target different data types (historical vs. forecast vs. current vs. regulatory lists) and different query parameters, making them easily distinguishable.
All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (e.g., get_annual_air_quality, get_aqi_forecast). The naming is uniform across all five tools, using snake_case throughout without any deviations in style or structure.
Five tools is reasonable for an EPA server covering air quality and toxics, but it feels slightly thin for the broad domain. The tools cover key areas, but additional tools for specific pollutants or detailed site data could enhance completeness without being overwhelming.
The server covers air quality (historical, forecast, current) and toxics (Superfund, TRI) well, but there are notable gaps. Missing operations include updates or deletions (not applicable here), but more critically, there's no tool for detailed pollutant analysis across locations or time-series queries beyond annual summaries, which limits agent flexibility.
get_annual_air_qualityInspectGet annual air quality summary data for a US state.
Returns annual statistics from the EPA Air Quality System (AQS),
including mean concentrations, max values, and exceedance counts
for the specified pollutant across all monitoring sites in the state.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'NY').
parameter: Pollutant to query. Options: 'PM2.5', 'Ozone', 'SO2', 'NO2', 'CO'.
Default is 'PM2.5'.
start_year: Start year for the query range (e.g. 2020). Default is 2020.
end_year: End year for the query range (e.g. 2023). Default is 2023.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | ||
| end_year | No | ||
| parameter | No | PM2.5 | |
| start_year | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_aqi_forecastInspectGet the air quality forecast for a ZIP code.
Returns forecast AQI values and health categories for upcoming days,
typically covering today and the next 1-2 days.
Args:
zip_code: US ZIP code (e.g. '20001').
| Name | Required | Description | Default |
|---|---|---|---|
| zip_code | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_current_aqiInspectGet 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).
| Name | Required | Description | Default |
|---|---|---|---|
| latitude | No | ||
| zip_code | No | ||
| longitude | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_superfund_sitesInspectGet active Superfund (National Priorities List) sites in a state.
Returns hazardous waste cleanup sites listed on the EPA's National
Priorities List, including site names, locations, and status information.
No API key required.
Args:
state: Two-letter US state abbreviation (e.g. 'NJ', 'CA').
limit: Maximum number of sites to return (default 50, max 500).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_tri_facilitiesInspectGet Toxics Release Inventory (TRI) facilities in a state.
Returns facilities that report toxic chemical releases to the EPA,
including facility names, addresses, and industry information.
No API key required.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX').
city: Optional city name to filter results.
limit: Maximum number of facilities to return (default 50, max 500).
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| limit | No | ||
| state | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!