Skip to main content
Glama

Epa Echo

by io.github.pipeworx-io

Echo Facility Search

echo_facility_search
Read-onlyIdempotent

Search EPA-regulated facilities by name, state, ZIP code, city, or industry code. facility_name uses a case-insensitive starts-with match; prepend % for a contains search (e.g., "%Exxon%" finds any facility with "Exxon" in its name). Combine at least two filters — a bare state is rejected upstream for large states ({state: "TX"} alone matches ~344,000 facilities and errors). Good queries: {facility_name: "%Exxon%", state: "TX"}, {city: "Baytown", state: "TX"}, {zip: "94025"}, {naics: "3251", state: "TX"}. Returns facility IDs, addresses, lat/long, compliance status, inspection/enforcement counts, and total penalties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoZIP code.
cityNoCity name (e.g., "Baytown").
limitNoMax results to return (default 20, max 100).
naicsNoNAICS industry code, 2-6 digits — prefix match (e.g., "3251" = basic chemical manufacturing). Pair with state; alone it matches too many facilities.
stateNoTwo-letter state abbreviation (e.g., "TX").
facility_nameNoFacility name — starts-with match by default; use % wildcard for contains search, e.g., "%Exxon%" or "%Baytown%".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
returnedYesNumber of facilities returned in this response
facilitiesYesList of EPA-regulated facilities
total_countYesTotal number of facilities matching search criteria

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / naics / description
      Previous value: -"NAICS industry code."New value: +"NAICS industry code, 2-6 digits — prefix match (e.g., \"3251\" = basic chemical manufacturing). Pair with state; alone it matches too many facilities."
  2. Changed3 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"City name."New value: +"City name (e.g., \"Baytown\")."
    • changedInput schema / properties / facility_name / description
      Previous value: -"Facility name (partial match)."New value: +"Facility name — starts-with match by default; use % wildcard for contains search, e.g., \"%Exxon%\" or \"%Baytown%\"."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state abbreviation (e.g., \"CA\")."New value: +"Two-letter state abbreviation (e.g., \"TX\")."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "facilities": {
+      "description": "List of EPA-regulated facilities",
+      "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"
+    },
+    "returned": {
+      "description": "Number of facilities returned in this response",
+      "type": "number"
+    },
+    "total_count": {
+      "description": "Total number of facilities matching search criteria",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_count",
+    "returned",
+    "facilities"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "facility_name": "Steel Mill",
+    "limit": 20,
+    "state": "PA"
+  },
+  {
+    "city": "Houston",
+    "limit": 50,
+    "naics": "3211",
+    "state": "TX"
+  }
+]
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds context: case-insensitive starts-with vs contains match, prefix matching for NAICS, mention of return fields (compliance status, inspection counts, penalties). No contradictions.

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?

The description is well-structured with examples and front-loaded purpose, but slightly long at ~150 words. Every sentence adds value, though some redundancy in examples could be trimmed. Still concise for the complexity.

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?

Given 6 parameters, 100% schema coverage, and presence of an output schema, the description covers all needed context: filter requirements, return fields, edge cases (large states, wildcard usage). Agent can accurately invoke the tool.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds critical semantic details beyond schema descriptions: facility_name's default starts-with behavior and % wildcard usage, NAICS prefix match, and the requirement to pair state with another filter. These add significant value.

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 clearly states the tool searches EPA-regulated facilities by multiple criteria, distinguishing it from sibling echo_* tools which focus on compliance history, enforcement actions, etc. The verb 'Search' paired with resource 'EPA-regulated facilities' is specific and unambiguous.

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 states when to use (search facilities), provides critical guidance on combining at least two filters, warns against bare state queries for large states, and gives concrete examples of good queries. This helps the agent avoid common errors.

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

All Epa Echo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded form a tight cluster, and the beta variant is explicitly identical to ask_pipeworx today. Several meta-tools like discover_tools, suggest_questions, and deep_research also overlap in discovery-oriented usage, so an agent must read carefully to pick the right one.

Naming Consistency3/5

Names are uniformly lowercase with underscores and mostly descriptive, but the conventions are mixed: verb_noun tools like validate_claim and list_subscriptions sit alongside noun_phrase tools like entity_profile and polymarket_arbitrage, plus bare verbs like remember and subscribe. It is readable but not a single predictable pattern.

Tool Count2/5

36 tools is well above the 25+ threshold, and the surface spans unrelated domains: EPA ECHO data, general Pipeworx research, Polymarket betting, memory, npm scanning, and AI visibility checks. For a server named 'Epa Echo', most tools feel out of scope and the collection seems like several separate servers merged together.

Completeness4/5

The EPA ECHO subset provides a solid facility-search, violations, compliance-history, and enforcement-action lifecycle. The broader Pipeworx surface also covers lookups, grounded answers, deep research, entity profiling, subscriptions, and memory, with only minor workaround-level gaps such as no dedicated ECHO permit/emissions detail tool.

Resources