Skip to main content
Glama

Epa Echo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Echo Compliance History

echo_compliance_history
Read-onlyIdempotent

Check a facility's compliance record and enforcement timeline. Returns violation status, inspection dates, quarters in violation, and enforcement actions taken.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
registry_idYesEPA Registry ID (from echo_facility_search results).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
registry_idYesEPA Registry ID for the facility
compliance_summaryYesFacility compliance summary data from EPA ECHO

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "registry_id": "110000350148"
-  }
-]New value: +[
+  {
+    "registry_id": "110037848498"
+  }
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "compliance_summary": {
+      "description": "Facility compliance summary data from EPA ECHO",
+      "type": "object"
+    },
+    "registry_id": {
+      "description": "EPA Registry ID for the facility",
+      "type": "string"
+    }
+  },
+  "required": [
+    "registry_id",
+    "compliance_summary"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "registry_id": "110000350148"
+  }
+]
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds what is returned but no additional behavioral context beyond annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with purpose, no wasted words.

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?

Output schema exists so return values are covered. Description lists typical outputs sufficiently for a simple lookup tool.

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?

Single parameter registry_id is fully described in schema (100% coverage). Description adds origin context ('from echo_facility_search results') but does not add new meaning beyond 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?

Description uses verb 'Check' with specific resource 'facility's compliance record' and enumerates specific outputs (violation status, inspection dates, etc.), clearly distinguishing from siblings like echo_violations or echo_enforcement_actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies prerequisite (registry_id from echo_facility_search) but no explicit guidance on when to use this vs alternatives like echo_enforcement_actions or echo_violations, which may overlap.

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.

Resources