EPA Air Quality & Toxics

get_tri_facilities

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

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_tri_facilities"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No
`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?

No annotations are provided, so the description carries the burden. It discloses that no API key is required, lists the returned data, and documents the limit constraint (default 50, max 500). It does not explicitly state read-only behavior, but 'Get' and 'Returns' strongly imply it, and there is 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 concise and well-structured. The purpose is front-loaded, followed by a brief behavior summary and a clear Args list. Every sentence provides useful information without redundancy.

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?

The tool is simple, and the description covers the query scope, output fields, and API key requirement. Since an output schema exists, the return values are further defined, and the description leaves no critical gaps for a getter tool of this complexity.

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%, and the description fully compensates: it explains state format ('two-letter US state abbreviation' with examples), clarifies city is optional, and specifies limit is the maximum number to return (default 50, max 500). This adds meaning beyond the schema's defaults.

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 retrieves TRI facilities in a state, naming specific fields returned (facility names, addresses, industry info). This action is distinct from sibling tools (air quality, superfund sites), so purpose is unambiguous.

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 clearly implies this tool is for querying TRI facilities by state, with optional city and limit filters. It does not explicitly name alternatives or exclusions, but the context and sibling tool names make it obvious that this is the TRI facility lookup tool.

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?