Skip to main content
Glama

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.

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": {
      "limit": 20,
      "state": "PA",
      "facility_name": "Steel Mill"
    },
    "name": "echo_facility_search"
  }
}

Input 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

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.

  1. Changed2 schema fields changed
    • changedInput schema / properties / facility_name / description
      Previous value: -"Facility name — starts-with match by default; use % wildcard for contains search, e.g., \"%Exxon%\" or \"%Baytown%\"."New value: +"Facility name, starts-with match by default; use % wildcard for contains search, e.g., \"%Exxon%\" or \"%Baytown%\"."
    • changedInput schema / properties / naics / description
      Previous value: -"NAICS industry code, 2-6 digits — prefix match (e.g., \"3251\" = basic chemical manufacturing). Pair with state; alone it matches too many facilities."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. 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."
  3. 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\")."
  4. 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"
      +}
  5. 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"
      +  }
      +]
  6. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds real value beyond that by disclosing upstream validation behavior (bare state errors for large states) and detail-level match semantics for facility_name. However, it omits pagination behavior, result ordering, and whether errors surface as empty results or exceptions, so it is useful rather than thorough.

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?

Front-loads the verb and searchable fields, then the matching semantics, then the hard constraint, then worked examples, then what is returned. No sentence is decorative; the examples are the shortest way to convey valid filter combinations.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes returned fields (IDs, addresses, lat/long, compliance status, counts, penalties). The only gap is that no-result and error semantics beyond the bare-state case are not described.

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 description coverage is 100%, so every parameter is already documented, which sets the baseline at 3. The description adds a cross-parameter constraint (at least two filters, since required is 0 in the schema) and the % wildcard convention, but repeats name/city/state/naics meanings that the schema already provides.

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?

States a specific verb and resource ('Search EPA-regulated facilities') and enumerates the searchable dimensions (name, state, ZIP, city, industry code), which separates it from violation-oriented siblings like echo_search_by_violation. It does not explicitly name an alternative tool, so sibling differentiation is implied by scope rather than stated.

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?

Gives concrete positive guidance: 'Combine at least two filters', warns that a bare state is rejected upstream for large states with a quantified example ({state: "TX"} matches ~344,000), and lists four good query shapes including a single-filter ZIP case. It lacks explicit when-not-to-use guidance pointing at sibling tools such as echo_search_by_violation, so the routing guidance is incomplete.

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.