epa-mcp-server

Get TRI Chemical Releases for Facility

epa_tri_get_facility_releases

Read-onlyIdempotent

TRI: Query Toxic Release Inventory annual chemical release data for a specific facility. Returns per-chemical release records with chemical name, reporting year, routine on-site releases by medium (air, water, land, underground injection), and the one-time / non-routine release quantity. Quantities are in pounds; dioxin and dioxin-like compounds, which TRI has facilities report in grams, are converted and marked with reportedUnit. TRI data lags ~18 months — the most recent available year is typically 2 years prior to the current calendar year. facility_id is the 15-character TRI facility ID: take it from the facilityId field of epa_tri_search_releases, which also identifies top emitters across a region, or from the triFacilityIds of epa_echo_get_facility for a facility you already hold a Registry ID for. A 12-digit EPA Registry ID is a different identifier and matches no TRI records.

Input Schema

Name	Required	Description
`year`	No	Reporting year to retrieve. Omit for all available years, newest first. At most 500 filings are returned; narrow with year or chemical_name when capped. TRI data is typically available through ~2 years prior to the current year.
`facility_id`	Yes	15-character TRI facility ID (e.g. "9867WSNRWD1981S") — the facilityId field returned by epa_tri_search_releases, or an entry of epa_echo_get_facility triFacilityIds. A 12-digit EPA Registry ID matches no TRI records.
`chemical_name`	No	Optional filter to restrict results to a specific chemical (partial match, case-insensitive). Commas, apostrophes, brackets, and Greek letters are matched as written, e.g. "4,4'-Methylenedianiline".

Output Schema

Name	Required	Description
`cap`	No	The 500-filing lookup cap, present only when reached.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of filings returned when capped.
`notice`	No	Present when a punctuated chemical_name filter read its page limit before finding every filing spelled as given, so more matching records may exist.
`message`	No	Recovery hint when no releases are found — suggests alternative years or checking the facility ID. Absent when releases are returned.
`guidance`	No	How to narrow a capped lookup with year or a more specific chemical_name.
`releases`	No	Per-chemical annual TRI release records for the queried facility
`truncated`	No	True when 500 filings were returned and more may exist.
`facilityId`	No	TRI facility ID queried

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the description's value-add is the domain caveats: ~18-month reporting lag, pound units with dioxin converted from grams and flagged via reportedUnit. It stops short of describing truncation/pagination behavior, though the 500-filing cap is documented in the schema rather than here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then return shape, units, latency caveat, and identifier sourcing — a sensible order with no filler sentences. Minor redundancy: the '12-digit EPA Registry ID matches no TRI records' warning repeats verbatim what the facility_id schema description already states.

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?

Output schema exists so return values needn't be enumerated, yet the description still summarizes the record shape and unit handling. Combined with the lag caveat and identifier sourcing, an agent has everything needed to call it correctly on the first try.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above that by giving the provenance and exact format of facility_id ('15-character TRI facility ID') and the negative case of the 12-digit Registry ID, which is the most likely invocation error. It adds little on year/chemical_name beyond what the schema says.

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?

States a specific verb and resource ('Query Toxic Release Inventory annual chemical release data for a specific facility') and immediately distinguishes itself from the sibling search tool by scoping to one facility. An agent can tell it apart from epa_tri_search_releases without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: get facility_id from epa_tri_search_releases (or from triFacilityIds of epa_echo_get_facility if the agent holds a Registry ID), and warns that a 12-digit Registry ID matches nothing. This is when-to-use plus how-to-source-the-key, with an explicit exclusion.

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

All epa-mcp-server 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.