Skip to main content
Glama

Search EPA Enforcement Cases

epa_echo_search_violations
Read-onlyIdempotent

ECHO: Search EPA civil and criminal enforcement cases by state, ZIP code, regulatory program, case type, or filing-date range. Returns case identifier, case type and status, lead agency (EPA or state), primary law and section, enforcement outcome, federal and state penalties, cost recovery, compliance action and SEP costs, and filing, settlement, and closing dates. Case rows name no facility: pass a civil caseId to epa_echo_get_case for the facilities, defendants, and settlements behind it. Designed for area-level violation discovery — for a single known facility's enforcement history use epa_echo_get_facility instead. At least one of state or zip_code is required. Page past limit with offset and nextOffset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "epa_echo_search_violations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of cases to return in one call. Default 25; a larger value returns at most 2,000 and says so. Page past it with offset and nextOffset.
stateNo2-letter state or territory codes where the case is located (e.g. "TX", "PR"), case-insensitive, matching any of them. A case spanning several states matches each of them and is returned once. ECHO also files some cases under codes outside the USPS set; any 2-character code is searched as written.
offsetNoNumber of cases to skip before this page (default 0). Pass the previous call's nextOffset to continue; a value past the end returns an empty page.
programNoFilter by regulatory program: CAA=Clean Air Act, CWA=Clean Water Act, RCRA=hazardous waste, SDWA=drinking water, CERCLA=Superfund, EPCRA=emergency planning and community right-to-know (the statute behind TRI), FIFRA=pesticides, TSCA=toxic substances. Matches any law a case cites, so a returned case's programsViolated (its primary law) can differ.
zip_codeNo5-digit ZIP codes of the case's facility locations, matching any of them; a ZIP+4 such as "98108-1234" searches its first five digits
case_typeNoFilter by case type: civil (regulatory violations), criminal (willful violations), or all. A filing-date range covers civil cases only: with a date, all returns civil cases and criminal is rejected.all
date_filed_endNoLatest filing date, inclusive (YYYY-MM-DD). Civil cases only. Omit, or pass "", for no upper bound.
date_filed_startNoEarliest filing date, inclusive (YYYY-MM-DD). Civil cases only. Omit, or pass "", for no lower bound.

Output Schema

NameRequiredDescriptionDefault
casesNoMatching cases, ECHO's order
errorNoPresent when the call failed. Absent on success.
noticeNoPresent when a filing-date range with case_type "all" dropped criminal cases, or when more cases follow (names the offset).
messageNoRecovery hint on an empty page; absent otherwise.
nextOffsetNoNext offset; absent on the last page.
totalCountNoMatches before limit and offset
limitNoticeNoPresent when a smaller limit than requested applied; says why.
effectiveQueryNoThe search as sent upstream, in input names: values, match modes, and result-changing defaults, "; "-joined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed37 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +25
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of cases to return in one call (1–100, default 50). A larger value, up to 5,000, returns 100 with a notice. Page past it with offset and nextOffset."New value: +"Number of cases to return in one call. Default 25; a larger value returns at most 2,000 and says so. Page past it with offset and nextOffset."
    • changedInput schema / properties / limit / maximum
      Previous value: -5000New value: +9007199254740991
    • changedInput schema / properties / state / description
      Previous value: -"2-letter state or territory code where the case is located (e.g. \"TX\", \"PR\"), case-insensitive. A case spanning several states matches each of them. ECHO also files some cases under codes outside the USPS set; any 2-character code is searched as written."New value: +"2-letter state or territory codes where the case is located (e.g. \"TX\", \"PR\"), case-insensitive, matching any of them. A case spanning several states matches each of them and is returned once. ECHO also files some cases under codes outside the USPS set; any 2-character code is searched as written."
    • addedInput schema / properties / state / items
      Added value: +{
      +  "pattern": "^\\s*[A-Za-z0-9]{2}\\s*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / state / maxItems
      Added value: +100
    • removedInput schema / properties / state / pattern
      Removed value: -"^\\s*(?:[A-Za-z0-9]{2}\\s*)?$"
    • changedInput schema / properties / state / type
      Previous value: -"string"New value: +"array"
    • changedInput schema / properties / zip_code / description
      Previous value: -"5-digit ZIP code of the case's facility location; a ZIP+4 such as \"98108-1234\" searches its first five digits"New value: +"5-digit ZIP codes of the case's facility locations, matching any of them; a ZIP+4 such as \"98108-1234\" searches its first five digits"
    • addedInput schema / properties / zip_code / items
      Added value: +{
      +  "pattern": "^\\s*\\d{5}(?:-?\\d{4})?\\s*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / zip_code / maxItems
      Added value: +200
    • removedInput schema / properties / zip_code / pattern
      Removed value: -"^\\s*(?:\\d{5}(?:-?\\d{4})?\\s*)?$"
    • changedInput schema / properties / zip_code / type
      Previous value: -"string"New value: +"array"
    • changedOutput schema / properties / cases / description
      Previous value: -"One page of matching enforcement cases, in ECHO's order: limit cases from offset"New value: +"Matching cases, ECHO's order"
    • changedOutput schema / properties / cases / items / description
      Previous value: -"EPA enforcement case record with case number, status, law, and outcome"New value: +"One case; caseStatus, enforcementOutcome, and the state/local penalty and cost fields are absent on criminal cases"
    • changedOutput schema / properties / cases / items / properties / caseId / description
      Previous value: -"Case number (e.g. \"03-2014-7010\"; criminal cases read \"CR_1270\") — pass a civil one to epa_echo_get_case"New value: +"Criminal ones start CR_; pass a civil one to epa_echo_get_case"
    • changedOutput schema / properties / cases / items / properties / caseStatus / description
      Previous value: -"Civil case status, e.g. \"Closed\", \"Final Order Issued\", \"Final Order Entered\", \"Complaint Filed\". Absent on criminal cases."New value: +"Civil status"
    • changedOutput schema / properties / cases / items / properties / caseType / description
      Previous value: -"Case category: \"Judicial\" or \"Administrative - Formal\" for civil cases, \"Criminal\" for every criminal case"New value: +"Civil: \"Judicial\" or \"Administrative - Formal\"; criminal: \"Criminal\""
    • changedOutput schema / properties / cases / items / properties / closedDate / description
      Previous value: -"Date the case was closed (MM/DD/YYYY). Absent while it is open."New value: +"MM/DD/YYYY; absent while open"
    • changedOutput schema / properties / cases / items / properties / complianceActionCostInDollars / description
      Previous value: -"Estimated cost of the injunctive relief and other actions required to return to compliance, in dollars. Absent on criminal cases."New value: +"Estimated cost of injunctive relief to return to compliance, in dollars"
    • changedOutput schema / properties / cases / items / properties / costRecoveryInDollars / description
      Previous value: -"Response costs the parties agreed or were ordered to repay, in dollars — the outcome of a CERCLA cost-recovery case. Absent on criminal cases."New value: +"Response costs agreed or ordered repaid (CERCLA), in dollars"
    • changedOutput schema / properties / cases / items / properties / enforcementOutcome / description
      Previous value: -"How the case was resolved, e.g. \"Final Order With Penalty\", \"Final Order No Penalty\". Absent when ECHO records none, and on criminal cases."New value: +"Resolution; absent when ECHO records none"
    • changedOutput schema / properties / cases / items / properties / filedDate / description
      Previous value: -"Date the enforcement case was filed (MM/DD/YYYY) — the date the filing-date range bounds"New value: +"MM/DD/YYYY; the date the filing-date range bounds"
    • changedOutput schema / properties / cases / items / properties / leadAgency / description
      Previous value: -"Agency leading the case: \"EPA\" or \"State\""New value: +"\"EPA\" or \"State\""
    • changedOutput schema / properties / cases / items / properties / penaltyAssessedInDollars / description
      Previous value: -"Federal penalty assessed in dollars (parsed from ECHO dollar string)"New value: +"Federal, in dollars"
    • changedOutput schema / properties / cases / items / properties / primarySection / description
      Previous value: -"Section of the primary law (e.g. \"107A\"); a criminal case cites the U.S. Code (e.g. \"33 U.S.C. 1908(a)\")"New value: +"Section of the primary law; criminal cases cite the U.S. Code"
    • changedOutput schema / properties / cases / items / properties / programsViolated / description
      Previous value: -"Primary regulatory law cited (e.g. \"CERCLA\", \"CAA\", \"CWA\")"New value: +"Primary law cited"
    • changedOutput schema / properties / cases / items / properties / settlementDate / description
      Previous value: -"Settlement or resolution date (MM/DD/YYYY)"New value: +"Settlement or resolution date, MM/DD/YYYY"
    • changedOutput schema / properties / cases / items / properties / stateLocalPenaltyInDollars / description
      Previous value: -"State or local penalty assessed in dollars. Absent on criminal cases."New value: +"State or local, in dollars"
    • changedOutput schema / properties / cases / items / properties / supplementalProjectCostInDollars / description
      Previous value: -"Cost of Supplemental Environmental Projects the parties agreed to, in dollars. Absent on criminal cases."New value: +"Agreed SEP cost, in dollars"
    • changedOutput schema / properties / effectiveQuery / description
      Previous value: -"The search as the server sent it upstream, in this tool's input names: normalized values, how each text filter matched (\"=\" exact, \"contains\", \"begins with\", \"has words\"), and defaults that change what comes back. Terms are separated by \"; \"."New value: +"The search as sent upstream, in input names: values, match modes, and result-changing defaults, \"; \"-joined."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `no_geographic_filter`: Neither state nor zip_code was provided. `invalid_date`: date_filed_start or date_filed_end is not a real calendar date, such as 2024-02-30. `date_range_inverted`: date_filed_start is later than date_filed_end. `criminal_date_filter`: case_type \"criminal\" was combined with a filing-date bound, which ECHO records for civil cases only. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_geographic_filter`: Neither state nor zip_code was given. `invalid_date`: A filing date is not a real calendar date. `date_range_inverted`: date_filed_start is after date_filed_end. `criminal_date_filter`: case_type \"criminal\" with a filing-date bound, which only civil cases carry. Other values are possible when a failure originates below the handler."
    • 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 the page is empty: no case matched, or offset is past the last match. Absent when cases are returned."New value: +"Recovery hint on an empty page; 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 filing-date range with case_type \"all\" left criminal cases out of the results, or when more cases follow (names the offset that continues the list)."New value: +"Present when a filing-date range with case_type \"all\" dropped criminal cases, or when more cases follow (names the offset)."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Cases matched before limit and offset were applied"New value: +"Matches before limit and offset"
  2. Changed31 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of cases to return (1–100)"New value: +"Maximum number of cases to return in one call (1–100, default 50). A larger value, up to 5,000, returns 100 with a notice. Page past it with offset and nextOffset."
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +5000
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of cases 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 / program / description
      Previous value: -"Filter by regulatory program: CAA=Clean Air Act, CWA=Clean Water Act, RCRA=hazardous waste, SDWA=drinking water, CERCLA=Superfund, FIFRA=pesticides, TSCA=toxic substances. Matches any law a case cites, so a returned case's programsViolated (its primary law) can differ."New value: +"Filter by regulatory program: CAA=Clean Air Act, CWA=Clean Water Act, RCRA=hazardous waste, SDWA=drinking water, CERCLA=Superfund, EPCRA=emergency planning and community right-to-know (the statute behind TRI), FIFRA=pesticides, TSCA=toxic substances. Matches any law a case cites, so a returned case's programsViolated (its primary law) can differ."
    • changedInput schema / properties / program / enum
      Previous value: -[
      -  "CAA",
      -  "CWA",
      -  "RCRA",
      -  "SDWA",
      -  "CERCLA",
      -  "FIFRA",
      -  "TSCA"
      -]New value: +[
      +  "CAA",
      +  "CWA",
      +  "RCRA",
      +  "SDWA",
      +  "CERCLA",
      +  "EPCRA",
      +  "FIFRA",
      +  "TSCA"
      +]
    • changedInput schema / properties / state / description
      Previous value: -"2-letter US state abbreviation to filter cases (e.g. \"TX\", \"CA\")"New value: +"2-letter state or territory code where the case is located (e.g. \"TX\", \"PR\"), case-insensitive. A case spanning several states matches each of them. ECHO also files some cases under codes outside the USPS set; any 2-character code is searched as written."
    • addedInput schema / properties / state / pattern
      Added value: +"^\\s*(?:[A-Za-z0-9]{2}\\s*)?$"
    • changedInput schema / properties / zip_code / description
      Previous value: -"5-digit ZIP code of the case's facility location"New value: +"5-digit ZIP code of the case's facility location; a ZIP+4 such as \"98108-1234\" searches its first five digits"
    • addedInput schema / properties / zip_code / pattern
      Added value: +"^\\s*(?:\\d{5}(?:-?\\d{4})?\\s*)?$"
    • changedOutput schema / properties / cases / description
      Previous value: -"Matching enforcement cases"New value: +"One page of matching enforcement cases, in ECHO's order: limit cases from offset"
    • changedOutput schema / properties / cases / items / description
      Previous value: -"EPA enforcement case record with case number, program, and penalty details"New value: +"EPA enforcement case record with case number, status, law, and outcome"
    • changedOutput schema / properties / cases / items / properties / caseId / description
      Previous value: -"Case number / docket identifier (e.g. \"03-2014-7010\") — primary case reference"New value: +"Case number (e.g. \"03-2014-7010\"; criminal cases read \"CR_1270\") — pass a civil one to epa_echo_get_case"
    • addedOutput schema / properties / cases / items / properties / caseStatus
      Added value: +{
      +  "description": "Civil case status, e.g. \"Closed\", \"Final Order Issued\", \"Final Order Entered\", \"Complaint Filed\". Absent on criminal cases.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / cases / items / properties / caseType / description
      Previous value: -"Case category (e.g. \"Judicial\", \"Administrative - Formal\")"New value: +"Case category: \"Judicial\" or \"Administrative - Formal\" for civil cases, \"Criminal\" for every criminal case"
    • addedOutput schema / properties / cases / items / properties / closedDate
      Added value: +{
      +  "description": "Date the case was closed (MM/DD/YYYY). Absent while it is open.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / cases / items / properties / complianceActionCostInDollars
      Added value: +{
      +  "description": "Estimated cost of the injunctive relief and other actions required to return to compliance, in dollars. Absent on criminal cases.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / cases / items / properties / costRecoveryInDollars
      Added value: +{
      +  "description": "Response costs the parties agreed or were ordered to repay, in dollars — the outcome of a CERCLA cost-recovery case. Absent on criminal cases.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / cases / items / properties / enforcementOutcome
      Added value: +{
      +  "description": "How the case was resolved, e.g. \"Final Order With Penalty\", \"Final Order No Penalty\". Absent when ECHO records none, and on criminal cases.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / cases / items / properties / facilityName
      Removed value: -{
      -  "description": "Regulated facility name — not available in ECHO enforcement case records; use epa_echo_get_facility with a Registry ID for facility details",
      -  "type": "string"
      -}
    • addedOutput schema / properties / cases / items / properties / leadAgency
      Added value: +{
      +  "description": "Agency leading the case: \"EPA\" or \"State\"",
      +  "type": "string"
      +}
    • addedOutput schema / properties / cases / items / properties / primarySection
      Added value: +{
      +  "description": "Section of the primary law (e.g. \"107A\"); a criminal case cites the U.S. Code (e.g. \"33 U.S.C. 1908(a)\")",
      +  "type": "string"
      +}
    • removedOutput schema / properties / cases / items / properties / registryId
      Removed value: -{
      -  "description": "EPA Registry ID — not returned in enforcement case search results; obtain via epa_echo_search_facilities",
      -  "type": "string"
      -}
    • removedOutput schema / properties / cases / items / properties / state
      Removed value: -{
      -  "description": "State where the facility is located — not returned in enforcement case search results",
      -  "type": "string"
      -}
    • addedOutput schema / properties / cases / items / properties / stateLocalPenaltyInDollars
      Added value: +{
      +  "description": "State or local penalty assessed in dollars. Absent on criminal cases.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / cases / items / properties / supplementalProjectCostInDollars
      Added value: +{
      +  "description": "Cost of Supplemental Environmental Projects the parties agreed to, in dollars. Absent on criminal cases.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / effectiveQuery
      Added value: +{
      +  "description": "The search as the server sent it upstream, in this tool's input names: normalized values, how each text filter matched (\"=\" exact, \"contains\", \"begins with\", \"has words\"), and defaults that change what comes back. Terms are separated by \"; \".",
      +  "type": "string"
      +}
    • addedOutput schema / properties / limitNotice
      Added value: +{
      +  "description": "Present when limit was above the cap and the call returned the cap instead.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / message / description
      Previous value: -"Recovery hint when no cases are found — echoes filters and suggests broadening. Absent when cases are returned."New value: +"Recovery hint when the page is empty: no case matched, or offset is past the last match. Absent when cases are returned."
    • 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"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"Present when a filing-date range with case_type \"all\" left criminal cases out of the results."New value: +"Present when a filing-date range with case_type \"all\" left criminal cases out of the results, or when more cases follow (names the offset that continues the list)."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Total cases matched before the limit was applied"New value: +"Cases matched before limit and offset were applied"
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, so the description's added value is real: the 2,000-row cap on limit, empty page when offset passes the end, civil-only restriction on filing-date ranges, and the important caveat that case rows carry no facility data. It stops short of describing response shape or ordering, but with an output schema present that is a minor gap.

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 the search scope, then return contents, then sibling routing, then constraints and paging. Dense but every sentence carries distinct information; the return-field enumeration is the longest clause and only marginally earns its length given 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?

For an 8-parameter search tool with full schema coverage, annotations, and an output schema, nothing an agent needs to call it correctly is missing: required precondition, paging, date-range limits, and where to go for facility detail are all present.

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 and the schema already explains program enums, ZIP+4 handling, and multi-state matching. The description earns above baseline by adding cross-parameter semantics the schema does not state: the state-or-zip_code requirement and the offset/nextOffset paging contract.

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 (search EPA civil and criminal enforcement cases) plus the filter axes (state, ZIP, program, case type, filing-date range). It explicitly distinguishes itself from two siblings: epa_echo_get_case for the facilities/defendants behind a case, and epa_echo_get_facility for a single known facility's history.

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?

Gives explicit when-to-use framing ("Designed for area-level violation discovery") and names the alternatives with the conditions that select them. It also states a hard precondition, "At least one of state or zip_code is required", which is guidance an agent cannot infer from the schema's empty required list.

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.