EPA Air Quality & Toxics

get_superfund_sites

Get 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).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "get_superfund_sites"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`state`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that 'No API key required' (auth requirement), returns active sites only, and provides a max limit of 500 beyond the schema. It does not mention rate limits or error behavior, but the added context about API key and constraints is meaningful.

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 well-structured: a one-line purpose, a brief return explanation, a note on API key, and a clear Args list. Every sentence adds value, and the front-loaded purpose makes it immediately scannable.

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?

Despite having an output schema, the description still clarifies the return contents (site names, locations, status). It covers the essential operational detail (no API key, parameter constraints) and is complete for a simple list-style tool with two parameters.

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?

Schema description coverage is 0%, so the description must compensate. The Args section adds clear meaning: state is a two-letter abbreviation, and limit is the maximum number of sites with default 50 and max 500. This fully explains both parameters beyond the raw schema.

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 starts with a clear, specific verb+resource+scope: 'Get active Superfund (National Priorities List) sites in a state.' It further explains that it returns hazardous waste cleanup sites with names, locations, and status. This clearly distinguishes it from siblings like air quality or TRI 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 clear context for when to use the tool (when Superfund/NPL site data for a state is needed) but does not explicitly mention alternatives or exclusions. It implies usage through the specific scope, but does not name sibling tools or state 'use this instead of X'.

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

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

Need Help?