Skip to main content
Glama

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, TRI chemical ID and CAS number, reporting year, on-site releases by medium (air, water, land, underground injection) and their total, and the Form R one-time release quantity, newest reporting year first; page through them with offset and nextOffset. 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, 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 fails validation.

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": {
      "facility_id": "<facility_id>"
    },
    "name": "epa_tri_get_facility_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoReporting year to retrieve. Omit for all available years, newest first. TRI data is typically available through ~2 years prior to the current year.
limitNoNumber of filings to return in one call. Default 25; a larger value returns at most 699 and says so. Page past it with offset and nextOffset.
offsetNoNumber of filings to skip before this page (default 0). Pass the previous call's nextOffset to continue; a value past the end returns an empty page.
chemical_idNoTRI chemical ID to match exactly, where chemical_name matches any name containing its text: a CAS Registry Number, hyphens and leading zeros optional, with a valid check digit; a TRI category code, N and three digits in any case; or a chemicalId an earlier result returned.
facility_idYes15-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. Case, surrounding whitespace, and end slashes are ignored; a 12-digit EPA Registry ID fails validation.
chemical_nameNoOptional 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

NameRequiredDescriptionDefault
capNoRequested limit after the cap; present only when truncated.
errorNoPresent when the call failed. Absent on success.
shownNoPresent only when truncated.
noticeNoPresent when a punctuated chemical_name filter hit its read limit first, so more matches may exist.
messageNoRecovery hint on an empty result; absent otherwise.
guidanceNoPresent when truncated: the continuing offset.
releasesNoPer-chemical annual filings
truncatedNoTrue when more filings may follow; absent on the last page.
facilityIdNoID queried, uppercased, without whitespace or slashes
nextOffsetNoNext offset; absent on the last page.
limitNoticeNoPresent when a smaller limit than requested applied; says why.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed31 schema fields changed
    • addedInput schema / properties / chemical_id
      Added value: +{
      +  "description": "TRI chemical ID to match exactly, where chemical_name matches any name containing its text: a CAS Registry Number, hyphens and leading zeros optional, with a valid check digit; a TRI category code, N and three digits in any case; or a chemicalId an earlier result returned.",
      +  "pattern": "^\\s*(?:(?:\\d{2,7}-\\d{2}-\\d|\\d{5,10}|[Nn]\\d{3}|MIXTURE|TRD SECRT|NA|INVALID)\\s*)?$",
      +  "type": "string"
      +}
    • changedInput schema / properties / facility_id / description
      Previous value: -"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."New value: +"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. Case, surrounding whitespace, and end slashes are ignored; a 12-digit EPA Registry ID fails validation."
    • removedInput schema / properties / facility_id / minLength
      Removed value: -1
    • addedInput schema / properties / facility_id / pattern
      Added value: +"^\\s*\\/*[0-9A-Za-z]{15}\\/*\\s*$"
    • changedInput schema / properties / limit / default
      Previous value: -500New value: +25
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of filings to return in one call (1–500, default 500). A larger value, up to 5,000, returns 500 with a notice. Page past it with offset and nextOffset."New value: +"Number of filings to return in one call. Default 25; a larger value returns at most 699 and says so. Page past it with offset and nextOffset."
    • changedInput schema / properties / limit / maximum
      Previous value: -5000New value: +9007199254740991
    • changedOutput schema / properties / cap / description
      Previous value: -"The limit that was applied. Present only when truncated."New value: +"Requested limit after the cap; present only when truncated."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `unmatchable_filter`: facility_id holds a character EPA's DMAP service cannot match exactly, or chemical_name has no letter or digit. `filter_too_long`: facility_id and chemical_name make a request longer than EPA's DMAP service accepts. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `unmatchable_filter`: chemical_name has no letter or digit. `filter_too_long`: chemical_name makes the request too long. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / facilityId / description
      Previous value: -"TRI facility ID queried"New value: +"ID queried, uppercased, without whitespace or slashes"
    • changedOutput schema / properties / guidance / description
      Previous value: -"Present when truncated: the offset that continues the lookup."New value: +"Present when truncated: the continuing offset."
    • changedOutput schema / properties / limitNotice / description
      Previous value: -"Present when limit was above the cap and the call returned the cap instead."New value: +"Present when a smaller limit than requested applied; says why."
    • changedOutput schema / properties / message / description
      Previous value: -"Recovery hint when no releases are found — suggests alternative years or checking the facility ID. Absent when releases are returned."New value: +"Recovery hint on an empty result; absent otherwise."
    • changedOutput schema / properties / nextOffset / description
      Previous value: -"Offset of the next page: present exactly when more records follow, absent on the last page. Pass it as offset to continue."New value: +"Next offset; absent on the last page."
    • changedOutput schema / properties / notice / description
      Previous value: -"Present when a punctuated chemical_name filter read its page limit before finding every filing spelled as given, so more matching records may exist."New value: +"Present when a punctuated chemical_name filter hit its read limit first, so more matches may exist."
    • changedOutput schema / properties / releases / description
      Previous value: -"Per-chemical annual TRI release records for the queried facility"New value: +"Per-chemical annual filings"
    • changedOutput schema / properties / releases / items / description
      Previous value: -"Per-chemical TRI release record for this facility and year"New value: +"One chemical-year filing"
    • addedOutput schema / properties / releases / items / properties / casNumber
      Added value: +{
      +  "description": "CAS Registry Number, hyphenated. Absent for a category code or placeholder.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / releases / items / properties / chemicalId
      Added value: +{
      +  "description": "TRI chemical ID (a 10-digit zero-padded CAS number, an N-prefixed category code, or a placeholder); pass it as chemical_id for an exact match. Absent when TRI records none.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / releases / items / properties / chemicalName / description
      Previous value: -"Chemical name as reported to TRI"New value: +"Name as reported to TRI"
    • changedOutput schema / properties / releases / items / properties / facilityId / description
      Previous value: -"TRI facility identifier"New value: +"TRI facility ID"
    • changedOutput schema / properties / releases / items / properties / oneTimeReleaseInLbs / description
      Previous value: -"Form R Section 8.8 one-time release quantity in pounds (remedial actions, catastrophic events, and other one-time events not associated with production). It is already counted in the per-medium releases and the off-site transfers, so it is never added to them."New value: +"Form R Section 8.8 one-time release quantity in pounds; already counted in the per-medium releases and off-site transfers, so never added to them."
    • changedOutput schema / properties / releases / items / properties / releasesToAirInLbs / description
      Previous value: -"On-site air releases (fugitive + stack emissions) in pounds, summed across air release types for this submission."New value: +"On-site fugitive + stack air, in pounds"
    • changedOutput schema / properties / releases / items / properties / releasesToLandInLbs / description
      Previous value: -"On-site land releases in pounds — landfills, land treatment, surface impoundment, and other on-site disposal, summed for this submission."New value: +"On-site, disposal included, in pounds"
    • changedOutput schema / properties / releases / items / properties / releasesToUndergroundInjectionInLbs / description
      Previous value: -"On-site releases via underground injection wells in pounds, summed across injection well classes for this submission."New value: +"On-site injection wells, all classes, in pounds"
    • changedOutput schema / properties / releases / items / properties / releasesToWaterInLbs / description
      Previous value: -"On-site releases to surface water in pounds, summed across all reported outfalls for this submission."New value: +"On-site, all outfalls, in pounds"
    • changedOutput schema / properties / releases / items / properties / reportedUnit / description
      Previous value: -"Present as \"grams\" when TRI had the facility report this chemical in grams (dioxin and dioxin-like compounds); its quantities here are converted to pounds (1 lb = 453.59237 g). Absent for chemicals reported in pounds."New value: +"\"grams\" when TRI has the chemical reported in grams (dioxin and dioxin-like compounds); quantities here are converted to pounds (1 lb = 453.59237 g). Absent otherwise."
    • changedOutput schema / properties / releases / items / properties / reportingYear / description
      Previous value: -"Year of the TRI submission"New value: +"TRI reporting year"
    • changedOutput schema / properties / releases / items / properties / totalOnSiteReleasesInLbs / description
      Previous value: -"Sum of the per-medium on-site releases present on this record (Form R Sections 5.1–5.5.4), in pounds. A medium TRI recorded only as a range code is left out, as it is from the per-medium fields; TRI's published on-site total counts a range at its midpoint, so it can be higher. Absent when no medium has a quantity."New value: +"Sum of the per-medium fields present, in pounds; absent when none has a quantity. Media reported only as a range code are left out; TRI's published total counts their midpoint, so it can be higher."
    • changedOutput schema / properties / shown / description
      Previous value: -"Number of filings returned. Present only when truncated."New value: +"Present only when truncated."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when more filings may follow this page; nextOffset continues it. Absent on the last page."New value: +"True when more filings may follow; absent on the last page."
  2. Changed18 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 500,
      +  "description": "Maximum number of filings to return in one call (1–500, default 500). A larger value, up to 5,000, returns 500 with a notice. Page past it with offset and nextOffset.",
      +  "maximum": 5000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of filings to skip before this page (default 0). Pass the previous call's nextOffset to continue; a value past the end returns an empty page.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / year / description
      Previous value: -"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."New value: +"Reporting year to retrieve. Omit for all available years, newest first. TRI data is typically available through ~2 years prior to the current year."
    • changedOutput schema / properties / cap / description
      Previous value: -"The 500-filing lookup cap, present only when reached."New value: +"The limit that was applied. Present only when truncated."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode."New value: +"Machine-readable failure mode. Declared by this tool: `unmatchable_filter`: facility_id holds a character EPA's DMAP service cannot match exactly, or chemical_name has no letter or digit. `filter_too_long`: facility_id and chemical_name make a request longer than EPA's DMAP service accepts. Other values are possible when a failure originates below the handler."
    • addedOutput schema / properties / error / properties / data / properties / reason / examples
      Added value: +[
      +  "unmatchable_filter",
      +  "filter_too_long"
      +]
    • changedOutput schema / properties / guidance / description
      Previous value: -"How to narrow a capped lookup with year or a more specific chemical_name."New value: +"Present when truncated: the offset that continues the lookup."
    • addedOutput schema / properties / limitNotice
      Added value: +{
      +  "description": "Present when limit was above the cap and the call returned the cap instead.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "Offset of the next page: present exactly when more records follow, absent on the last page. Pass it as offset to continue.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / releases / items / properties / oneTimeReleaseInLbs
      Added value: +{
      +  "description": "Form R Section 8.8 one-time release quantity in pounds (remedial actions, catastrophic events, and other one-time events not associated with production). It is already counted in the per-medium releases and the off-site transfers, so it is never added to them.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / releases / items / properties / releasesToAirInLbs / description
      Previous value: -"On-site routine air releases (fugitive + stack emissions) in pounds, summed across air release types for this submission."New value: +"On-site air releases (fugitive + stack emissions) in pounds, summed across air release types for this submission."
    • changedOutput schema / properties / releases / items / properties / releasesToLandInLbs / description
      Previous value: -"On-site routine land releases in pounds — landfills, land treatment, surface impoundment, and other on-site disposal, summed for this submission."New value: +"On-site land releases in pounds — landfills, land treatment, surface impoundment, and other on-site disposal, summed for this submission."
    • changedOutput schema / properties / releases / items / properties / releasesToUndergroundInjectionInLbs / description
      Previous value: -"On-site routine releases via underground injection wells in pounds, summed across injection well classes for this submission."New value: +"On-site releases via underground injection wells in pounds, summed across injection well classes for this submission."
    • changedOutput schema / properties / releases / items / properties / releasesToWaterInLbs / description
      Previous value: -"On-site routine releases to surface water in pounds, summed across all reported outfalls for this submission."New value: +"On-site releases to surface water in pounds, summed across all reported outfalls for this submission."
    • addedOutput schema / properties / releases / items / properties / totalOnSiteReleasesInLbs
      Added value: +{
      +  "description": "Sum of the per-medium on-site releases present on this record (Form R Sections 5.1–5.5.4), in pounds. A medium TRI recorded only as a range code is left out, as it is from the per-medium fields; TRI's published on-site total counts a range at its midpoint, so it can be higher. Absent when no medium has a quantity.",
      +  "type": "number"
      +}
    • removedOutput schema / properties / releases / items / properties / totalReleasesInLbs
      Removed value: -{
      -  "description": "TRI one-time / non-routine release quantity in pounds (spills, accidents) — a distinct TRI category, NOT the sum of the per-medium routine releases below.",
      -  "type": "number"
      -}
    • changedOutput schema / properties / shown / description
      Previous value: -"Number of filings returned when capped."New value: +"Number of filings returned. Present only when truncated."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when 500 filings were returned and more may exist."New value: +"True when more filings may follow this page; nextOffset continues it. Absent on the last page."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds substantial behavior beyond them: newest-first ordering, offset/nextOffset paging, quantities in pounds with dioxin grams converted and flagged via reportedUnit, and a ~18-month data lag that bounds the most recent available year. These are operational facts an agent cannot get from the annotations.

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?

Purpose is front-loaded in the first clause, followed by return shape, pagination, units, temporal caveat, and ID sourcing in a logical order. The block is dense and long-ish, but nearly every sentence carries non-redundant information; only the return-value enumeration partially overlaps the output schema.

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 an output schema existing, the description supplies the temporal, unit, and identifier-provenance context an agent needs to call this correctly on the first try. Nothing material for correct invocation is missing.

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 the baseline is 3, but the description adds real meaning: facility_id format provenance and the failure mode for Registry IDs, the year-availability lag, and pagination flow via nextOffset. It reinforces rather than duplicates the schema, though most per-parameter syntax still lives in the 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?

States a specific verb and resource ('Query Toxic Release Inventory annual chemical release data for a specific facility') and immediately delineates scope: per-facility retrieval, as opposed to the search-based sibling epa_tri_search_releases. An agent can distinguish it from siblings without opening the schema.

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?

Gives concrete routing guidance for the required identifier: take facility_id from epa_tri_search_releases or from triFacilityIds of epa_echo_get_facility, and warns that a 12-digit Registry ID fails. It does not explicitly state the inverse condition ('use search_releases when you don't have an ID'), so the when-not guidance is inferred rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.