Skip to main content
Glama

Echo Search By Violation

echo_search_by_violation
Read-onlyIdempotent

Find EPA-regulated facilities currently flagged with an identified violation, filterable by state and environmental program (CWA/CAA/RCRA/ALL). EPA ECHO has no server-side violation filter, so this scans up to 1,000 facilities for the state and returns the ones in violation, it is a sample, not an exhaustive statewide count. Returns facility IDs, names, addresses, and compliance status per program.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "DE",
      "program": "CWA"
    },
    "name": "echo_search_by_violation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 20, max 100).
stateNoTwo-letter state abbreviation (e.g., "TX").
programNoProgram filter: "CWA", "CAA", "RCRA", or "ALL" (default "ALL").

Output Schema

NameRequiredDescriptionDefault
programYesProgram filter applied (CWA, CAA, RCRA, or ALL)
returnedYesNumber of facilities returned in this response
facilitiesYesList of facilities in significant non-compliance
total_countYesTotal number of facilities in significant non-compliance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "program": "CWA",
      -    "state": "CA"
      -  },
      -  {
      -    "limit": 100,
      -    "state": "TX"
      -  }
      -]New value: +[
      +  {
      +    "program": "CWA",
      +    "state": "DE"
      +  },
      +  {
      +    "limit": 20,
      +    "state": "VT"
      +  }
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "facilities": {
      +      "description": "List of facilities in significant non-compliance",
      +      "items": {
      +        "properties": {
      +          "caa_status": {
      +            "description": "Clean Air Act compliance status",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "city": {
      +            "description": "City name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "cwa_status": {
      +            "description": "Clean Water Act compliance status",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "formal_action_count": {
      +            "description": "Number of formal enforcement actions",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "inspection_count": {
      +            "description": "Total number of inspections",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "latitude": {
      +            "description": "Geographic latitude",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "longitude": {
      +            "description": "Geographic longitude",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "naics_codes": {
      +            "description": "North American Industry Classification System codes",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "description": "Facility name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "quarters_in_noncompliance": {
      +            "description": "Number of quarters facility was in non-compliance",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "rcra_status": {
      +            "description": "Resource Conservation and Recovery Act compliance status",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "registry_id": {
      +            "description": "EPA Registry ID for the facility",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "sdwis_status": {
      +            "description": "Safe Drinking Water Information System status",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "sic_codes": {
      +            "description": "Standard Industrial Classification codes",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "state": {
      +            "description": "State abbreviation",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "street": {
      +            "description": "Street address",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "total_penalties": {
      +            "description": "Total penalties assessed in dollars",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "zip": {
      +            "description": "ZIP code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "program": {
      +      "description": "Program filter applied (CWA, CAA, RCRA, or ALL)",
      +      "type": "string"
      +    },
      +    "returned": {
      +      "description": "Number of facilities returned in this response",
      +      "type": "number"
      +    },
      +    "total_count": {
      +      "description": "Total number of facilities in significant non-compliance",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "total_count",
      +    "returned",
      +    "program",
      +    "facilities"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "program": "CWA",
      +    "state": "CA"
      +  },
      +  {
      +    "limit": 100,
      +    "state": "TX"
      +  }
      +]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: there is no server-side violation filter, so it scans up to 1,000 facilities and returns only the violating subset, and the result is a sample rather than a full count. That sampling/truncation caveat is exactly the kind of detail annotations cannot convey.

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?

Two sentences, front-loaded with the purpose and followed by the key limitation and return fields. The second sentence is dense but every clause (scan cap, sampling caveat, returned fields) carries information. Minor tightening possible but no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and an output schema covering return shape, the description supplies the remaining essentials: filter dimensions, the sampling limitation, and the scan ceiling. The only mild ambiguity is the relationship between the 1,000-facility scan and the limit parameter's 100 cap, which an agent must infer.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents limit, state, and program, including the ALL default and the enum-like values. The description reinforces the state and program filtering semantics but adds no format or edge-case detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Find EPA-regulated facilities currently flagged with an identified violation,' with explicit state and program filters. It is clearly distinct from a plain facility lookup, though it never names the closest siblings (echo_violations, echo_facility_search) to route an agent between them.

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?

It gives clear context for when this tool fits: the user wants facilities with an active violation, scoped by state and program. It also adds an important caveat that results are a sample, not an exhaustive statewide count, which shapes expectations. There is no explicit exclusion or named alternative, so it stops short of a 5.

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.