Skip to main content
Glama

KeyVex

get_epa_enforcement

Read-only

Returns EPA federal CIVIL enforcement cases from ICIS FE&C (the EPA's Integrated Compliance Information System) via the ECHO bulk download — ~135K cases, EPA-lead administrative and judicial civil actions. CRIMINAL prosecutions are NOT in this source, and neither are state-lead actions. Refreshed weekly by EPA (~Saturday). Use this when the user asks about: EPA fines / penalties against a company, Clean Air Act / Clean Water Act / RCRA / Superfund enforcement, environmental violations by facility or state, settlements and consent decrees, or supplemental environmental projects (SEPs). Record shape (one doc per case, joins pre-flattened): case_number (RR-YYYY-NNNN), case_name, defendants[] (names), statutes[] + primary_statute (CWA, CAA, FIFRA, SDWA, RCRA, TSCA, CERCLA, EPCRA), activity_type ('administrative' | 'judicial'), activity_status + status_date, penalties from the CASE_PENALTIES table — fed_penalty, state_local_penalty, sep_amount, compliance_action_cost, cost recoveries, penalty_collected — settlement_lodged_date (earliest; only ~34% of cases lodge, mostly judicial) + settlement_entered_date (latest) + settlements_count, facilities[] (name, city, state, NAICS, FRS registry ID), region_code, doj_docket_number, enf_outcome, voluntary_self_disclosure, multimedia, summary_text, and source_url (the ECHO case report page). Date filters (since/until) and the default sort use status_date — the case's last status-change date, present on every case. Sorting by fed_penalty cannot be combined with since/until (numeric field). Cross-source: pair with get_enforcement_actions (press-release actions from 8 other regulators), get_federal_contracts (whether an EPA defendant still wins federal awards), and get_material_events (8-K environmental-liability disclosures). Pure-publisher posture: EPA's case records as published — no derived severity scores or compliance opinions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum records to return. Default 50, max 500.
sinceNostatus_date lower bound (YYYY-MM-DD inclusive).
stateNoTwo-letter state code of a named facility (e.g., 'TX'). Derived from the case's facilities.
untilNostatus_date upper bound (YYYY-MM-DD inclusive).
sort_byNoDefault: status_date. fed_penalty surfaces the largest federal penalties (cannot be combined with since/until).
sort_orderNoDefault: desc.
case_numberNoDirect lookup by ICIS case number, format RR-YYYY-NNNN (e.g., 'HQ-1998-0303').
fiscal_yearNoEPA fiscal year of the case (e.g., 2024).
min_penaltyNoOnly cases with fed_penalty >= this amount (USD).
activity_typeNoadministrative = EPA's own formal actions (~93% of cases); judicial = DOJ-filed civil court cases.
defendant_nameNoCase-insensitive substring against defendant names + case name (e.g., 'caterpillar', 'exxon').
primary_statuteNoLead statute code (RANK_ORDER=1): CWA (Clean Water Act), CAA (Clean Air Act), FIFRA (pesticides), SDWA (drinking water), RCRA (hazardous waste), TSCA (toxic substances), CERCLA (Superfund), EPCRA (right-to-know). Rare others: AIM, MPRSA, MWTA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable non-obvious behavior: refresh cadence (weekly, ~Saturday), publisher posture with no derived severity scores, source exclusion constraints, and the sort_by/filter incompatibility. It doesn't discuss pagination depth or result-size limits beyond the schema, which keeps it short of a 5.

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 source identity and exclusions, followed by use-cases, record shape, and filter caveats in a logical order. It is long and information-dense, but nearly every clause earns its place; the record-shape enumeration is the bulkiest part and slightly exceeds what an agent needs upfront.

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 a 12-parameter read-only query tool with no output schema, the description covers source scope, exclusions, refresh timing, record semantics (including which fields join pre-flattened), date-filter semantics, sort restrictions, and cross-source complements. Nothing an agent needs to invoke it correctly 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 baseline would be 3, but the description adds meaningful semantics beyond the schema: status_date is defined as the case's last status-change date present on every case, fed_penalty cannot be combined with since/until, and the settlement-lodging prevalence (~34%, mostly judicial) is surfaced. That is genuine added meaning over the structured fields.

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 names a specific verb (Returns) and resource (EPA federal civil enforcement cases from ICIS FE&C via ECHO bulk download), quantifies scope (~135K cases), and explicitly distinguishes this source from siblings by excluding criminal prosecutions and state-lead actions. An agent can immediately tell it apart from get_enforcement_actions and get_osha_enforcement.

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?

It gives an explicit when-to-use trigger list (EPA fines, CAA/CWA/RCRA/Superfund enforcement, settlements, SEPs) plus explicit exclusions and cross-source pairing guidance (get_enforcement_actions, get_federal_contracts, get_material_events). This is close to ideal routing guidance.

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.

Resources