Skip to main content
Glama

Search Superfund Sites

epa_superfund_search_sites
Read-onlyIdempotent

Superfund: Search Superfund (CERCLA/SEMS) sites by location, site name, or NPL listing status. Returns site identifiers, source NPL status labels, non-NPL assessment and archive metadata when available, coordinates, and county FIPS code. A state, city, ZIP, or name search returns sites in SEMS site ID order; latitude+longitude+radius returns them nearest first with each site's distanceMiles, and name narrows either. Page through a large match with offset and nextOffset. Proximity searches match only sites with usable coordinates and share a 50-second deadline; narrow the radius or add filters if the search times out. Use epa_superfund_get_site with a returned siteId for contaminant associations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "epa_superfund_search_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (partial match within state, case-insensitive). Punctuation is matched as written ("St. Louis", "Coeur d'Alene").
nameNoSite name (partial match, case-insensitive), alone or with any other filter. Punctuation is matched as written.
limitNoNumber of sites to return in one call. Default 25; a larger value returns at most 2,500 and says so. Page past it with offset and nextOffset.
stateNo2-letter US state or territory code to filter sites, e.g. "WA"
offsetNoNumber of sites to skip before this page (default 0). Pass the previous call's nextOffset to continue; a value past the end returns an empty page.
latitudeNoLatitude for proximity search (use with longitude and radius_miles)
zip_codeNo5-digit ZIP code to filter sites; a ZIP+4 searches its 5-digit ZIP. Matches sites recorded under the ZIP or any ZIP+4 within it.
longitudeNoLongitude for proximity search (use with latitude and radius_miles)
npl_statusNoFilter by NPL status: listed=final or part of an NPL site (F,A), not-listed=N, proposed=P, deleted=D, removed=R, withdrawn=W, all=include allall
radius_milesNoSearch radius in miles from the given coordinates. Required when using latitude+longitude.
exclude_archivedNoExclude archived sites by requiring SEMS archived_ind=N; false retains all archive statuses

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
sitesNoMatching sites
noticeNoProximity coordinate-coverage caveat with the page's place in the nearest-first match; also present when a punctuated city or name filter hits its page limit.
messageNoRecovery hint on an empty result; absent otherwise.
guidanceNoPresent when more sites follow: the continuing offset.
nextOffsetNoNext offset; absent on the last page.
totalCountNoMatches before limit and offset; present only on a proximity search (otherwise follow nextOffset).
limitNoticeNoPresent when a smaller limit than requested applied; says why.
effectiveQueryNoThe search as sent upstream, in input names: values, match modes, and result-changing defaults, "; "-joined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +25
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of sites to return in one call (1–200, default 50). A larger value, up to 5,000, returns 200 with a notice. Page past it with offset and nextOffset."New value: +"Number of sites to return in one call. Default 25; a larger value returns at most 2,500 and says so. Page past it with offset and nextOffset."
    • changedInput schema / properties / limit / maximum
      Previous value: -5000New value: +9007199254740991
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Site name (partial match, case-insensitive), alone or with any other filter. Punctuation is matched as written.",
      +  "maxLength": 4094,
      +  "type": "string"
      +}
    • changedOutput schema / properties / effectiveQuery / description
      Previous value: -"The search as the server sent it upstream, in this tool's input names: normalized values, how each text filter matched (\"=\" exact, \"contains\", \"begins with\", \"has words\"), and defaults that change what comes back. Terms are separated by \"; \"."New value: +"The search as sent upstream, in input names: values, match modes, and result-changing defaults, \"; \"-joined."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `incomplete_proximity`: Only part of latitude, longitude, and radius_miles was supplied, except latitude+longitude without radius_miles. `no_location_filter`: No location filter (state, city, zip_code, or latitude+longitude) was provided. `radius_required`: Latitude and longitude were provided without radius_miles. `invalid_state`: state has the 2-character form but is not a US state, DC, territory, freely associated state, UM, NN, or EPA region code. `unmatchable_filter`: city has no letter or digit for EPA's DMAP service to match on. `filter_too_long`: city makes a request longer than EPA's DMAP service accepts. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `incomplete_proximity`: A proximity input came without both latitude and longitude. `no_location_filter`: No state, city, zip_code, name, or latitude+longitude. `radius_required`: latitude and longitude without radius_miles. `invalid_state`: state is not a US state, territory, or EPA region code. `unmatchable_filter`: city or name has no letter or digit. `filter_too_long`: city or name makes the request too long. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / guidance / description
      Previous value: -"Present when more sites follow: the offset that continues the search."New value: +"Present when more sites follow: the continuing offset."
    • changedOutput schema / properties / limitNotice / description
      Previous value: -"Present when limit was above the cap and the call returned the cap instead."New value: +"Present when a smaller limit than requested applied; says why."
    • changedOutput schema / properties / message / description
      Previous value: -"Recovery hint when no sites are found. Absent when sites are returned."New value: +"Recovery hint on an empty result; absent otherwise."
    • changedOutput schema / properties / nextOffset / description
      Previous value: -"Offset of the next page: present exactly when more records follow, absent on the last page. Pass it as offset to continue."New value: +"Next offset; absent on the last page."
    • changedOutput schema / properties / notice / description
      Previous value: -"Proximity coordinate-coverage limitation, with the page's place in the nearest-first match when the page does not hold every match; also present when a non-proximity punctuated city filter reaches its page limit."New value: +"Proximity coordinate-coverage caveat with the page's place in the nearest-first match; also present when a punctuated city or name filter hits its page limit."
    • changedOutput schema / properties / sites / description
      Previous value: -"Matching Superfund sites"New value: +"Matching sites"
    • changedOutput schema / properties / sites / items / description
      Previous value: -"Superfund site record with source status and assessment metadata"New value: +"One site"
    • changedOutput schema / properties / sites / items / properties / archivedInd / description
      Previous value: -"Raw SEMS archive indicator, such as Y or N"New value: +"Y or N"
    • addedOutput schema / properties / sites / items / properties / distanceMiles
      Added value: +{
      +  "description": "Great-circle miles from the search point, to two decimals; absent without a search point or row coordinates.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / sites / items / properties / epaId / description
      Previous value: -"EPA site identifier distinct from the SEMS site ID"New value: +"EPA ID, distinct from siteId"
    • changedOutput schema / properties / sites / items / properties / federalFacilityInd / description
      Previous value: -"Raw SEMS federal facility indicator, such as Y or N"New value: +"Y or N"
    • changedOutput schema / properties / sites / items / properties / latitude / description
      Previous value: -"Latitude in decimal degrees"New value: +"Decimal degrees"
    • changedOutput schema / properties / sites / items / properties / longitude / description
      Previous value: -"Longitude in decimal degrees"New value: +"Decimal degrees"
    • changedOutput schema / properties / sites / items / properties / name / description
      Previous value: -"Superfund site name"New value: +"Site name"
    • changedOutput schema / properties / sites / items / properties / nonNplStatusName / description
      Previous value: -"Non-NPL assessment label reported by SEMS; not cleanup progress"New value: +"Non-NPL assessment label; not cleanup progress"
    • changedOutput schema / properties / sites / items / properties / nplStatus / description
      Previous value: -"Raw NPL code: F=final, A=part of an NPL site, N=not listed, P=proposed, D=deleted, R=removed, W=withdrawn"New value: +"F final, A part of an NPL site, N not listed, P proposed, D deleted, R removed, W withdrawn"
    • changedOutput schema / properties / sites / items / properties / nplStatusName / description
      Previous value: -"NPL status label reported by SEMS"New value: +"NPL status label"
    • changedOutput schema / properties / sites / items / properties / siteId / description
      Previous value: -"EPA SEMS site identifier"New value: +"SEMS site ID"
    • changedOutput schema / properties / sites / items / properties / state / description
      Previous value: -"2-letter state abbreviation"New value: +"State code"
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Superfund sites matched before limit and offset. Present for a proximity search, which ranks every match; absent for a state, city, or ZIP search, whose match count EPA's DMAP service does not report (follow nextOffset instead)."New value: +"Matches before limit and offset; present only on a proximity search (otherwise follow nextOffset)."
  2. Changed16 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of sites to return (1–200)"New value: +"Maximum number of sites to return in one call (1–200, default 50). A larger value, up to 5,000, returns 200 with a notice. Page past it with offset and nextOffset."
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +5000
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of sites to skip before this page (default 0). Pass the previous call's nextOffset to continue; a value past the end returns an empty page.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / state / description
      Previous value: -"2-letter US state abbreviation to filter sites"New value: +"2-letter US state or territory code to filter sites, e.g. \"WA\""
    • addedInput schema / properties / state / pattern
      Added value: +"^\\s*(?:[A-Za-z0-9]{2}\\s*)?$"
    • changedInput schema / properties / zip_code / description
      Previous value: -"5-digit ZIP code to filter sites"New value: +"5-digit ZIP code to filter sites; a ZIP+4 searches its 5-digit ZIP. Matches sites recorded under the ZIP or any ZIP+4 within it."
    • addedInput schema / properties / zip_code / pattern
      Added value: +"^\\s*(?:\\d{5}(?:-?\\d{4})?\\s*)?$"
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "sites",
      -      "totalCount"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "sites"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / effectiveQuery
      Added value: +{
      +  "description": "The search as the server sent it upstream, in this tool's input names: normalized values, how each text filter matched (\"=\" exact, \"contains\", \"begins with\", \"has words\"), and defaults that change what comes back. Terms are separated by \"; \".",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `incomplete_proximity`: Only part of latitude, longitude, and radius_miles was supplied, except latitude+longitude without radius_miles. `no_location_filter`: No location filter (state, city, zip_code, or latitude+longitude) was provided. `radius_required`: Latitude and longitude were provided without radius_miles. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `incomplete_proximity`: Only part of latitude, longitude, and radius_miles was supplied, except latitude+longitude without radius_miles. `no_location_filter`: No location filter (state, city, zip_code, or latitude+longitude) was provided. `radius_required`: Latitude and longitude were provided without radius_miles. `invalid_state`: state has the 2-character form but is not a US state, DC, territory, freely associated state, UM, NN, or EPA region code. `unmatchable_filter`: city has no letter or digit for EPA's DMAP service to match on. `filter_too_long`: city makes a request longer than EPA's DMAP service accepts. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "incomplete_proximity",
      -  "no_location_filter",
      -  "radius_required"
      -]New value: +[
      +  "incomplete_proximity",
      +  "no_location_filter",
      +  "radius_required",
      +  "invalid_state",
      +  "unmatchable_filter",
      +  "filter_too_long"
      +]
    • addedOutput schema / properties / guidance
      Added value: +{
      +  "description": "Present when more sites follow: the offset that continues the search.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / limitNotice
      Added value: +{
      +  "description": "Present when limit was above the cap and the call returned the cap instead.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "Offset of the next page: present exactly when more records follow, absent on the last page. Pass it as offset to continue.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"Proximity coordinate-coverage limitation, combined with any omitted-match notice; also present when a non-proximity punctuated city filter reaches its page limit."New value: +"Proximity coordinate-coverage limitation, with the page's place in the nearest-first match when the page does not hold every match; also present when a non-proximity punctuated city filter reaches its page limit."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Number of sites returned (may be less than available if limit applied)"New value: +"Superfund sites matched before limit and offset. Present for a proximity search, which ranks every match; absent for a state, city, or ZIP search, whose match count EPA's DMAP service does not report (follow nextOffset instead)."
  3. Changed18 schema fields changed
    • addedInput schema / properties / exclude_archived
      Added value: +{
      +  "default": false,
      +  "description": "Exclude archived sites by requiring SEMS archived_ind=N; false retains all archive statuses",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / latitude / maximum
      Added value: +90
    • addedInput schema / properties / latitude / minimum
      Added value: +-90
    • addedInput schema / properties / longitude / maximum
      Added value: +180
    • addedInput schema / properties / longitude / minimum
      Added value: +-180
    • changedInput schema / properties / npl_status / description
      Previous value: -"Filter by NPL (National Priorities List) status: listed=final NPL, not-listed=not on NPL, proposed=proposed for listing, all=include all"New value: +"Filter by NPL status: listed=final or part of an NPL site (F,A), not-listed=N, proposed=P, deleted=D, removed=R, withdrawn=W, all=include all"
    • changedInput schema / properties / npl_status / enum
      Previous value: -[
      -  "listed",
      -  "not-listed",
      -  "proposed",
      -  "all"
      -]New value: +[
      +  "listed",
      +  "not-listed",
      +  "proposed",
      +  "deleted",
      +  "removed",
      +  "withdrawn",
      +  "all"
      +]
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `no_location_filter`: No location filter (state, city, zip_code, or latitude+longitude) was provided. `radius_required`: Latitude and longitude were provided without radius_miles. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `incomplete_proximity`: Only part of latitude, longitude, and radius_miles was supplied, except latitude+longitude without radius_miles. `no_location_filter`: No location filter (state, city, zip_code, or latitude+longitude) was provided. `radius_required`: Latitude and longitude were provided without radius_miles. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "no_location_filter",
      -  "radius_required"
      -]New value: +[
      +  "incomplete_proximity",
      +  "no_location_filter",
      +  "radius_required"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Present when the result limit omits nearby sites or a non-proximity punctuated city filter reaches its page limit. Explains which matching sites were not returned."New value: +"Proximity coordinate-coverage limitation, combined with any omitted-match notice; also present when a non-proximity punctuated city filter reaches its page limit."
    • changedOutput schema / properties / sites / items / description
      Previous value: -"Superfund site record with location, NPL status, and cleanup status"New value: +"Superfund site record with source status and assessment metadata"
    • addedOutput schema / properties / sites / items / properties / archivedInd
      Added value: +{
      +  "description": "Raw SEMS archive indicator, such as Y or N",
      +  "type": "string"
      +}
    • removedOutput schema / properties / sites / items / properties / cleanupStatus
      Removed value: -{
      -  "description": "Current cleanup stage or status",
      -  "type": "string"
      -}
    • addedOutput schema / properties / sites / items / properties / epaId
      Added value: +{
      +  "description": "EPA site identifier distinct from the SEMS site ID",
      +  "type": "string"
      +}
    • addedOutput schema / properties / sites / items / properties / federalFacilityInd
      Added value: +{
      +  "description": "Raw SEMS federal facility indicator, such as Y or N",
      +  "type": "string"
      +}
    • addedOutput schema / properties / sites / items / properties / nonNplStatusName
      Added value: +{
      +  "description": "Non-NPL assessment label reported by SEMS; not cleanup progress",
      +  "type": "string"
      +}
    • changedOutput schema / properties / sites / items / properties / nplStatus / description
      Previous value: -"NPL status code: NPL=listed, N=not listed, P=proposed"New value: +"Raw NPL code: F=final, A=part of an NPL site, N=not listed, P=proposed, D=deleted, R=removed, W=withdrawn"
    • addedOutput schema / properties / sites / items / properties / nplStatusName
      Added value: +{
      +  "description": "NPL status label reported by SEMS",
      +  "type": "string"
      +}
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses result ordering by search mode (SEMS ID order versus nearest-first with distanceMiles), pagination via offset and nextOffset, a 2,500 row cap, and the constraint that proximity searches only match sites with usable coordinates. The timeout caveat adds useful operational context that annotations alone do not 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?

The description is front-loaded with purpose, then return fields, ordering, pagination, and caveats in a logical sequence with no filler. It is dense and slightly run-on in places, but every sentence contributes actionable information.

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 an 11-parameter, read-only search tool with full schema coverage, annotations, and an output schema, the description covers what an agent needs: how to search, return ordering, pagination, timeout behavior, and the follow-up tool for site details. Nothing critical for correct invocation appears to be 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?

With 100% schema coverage the baseline is 3, and the description adds meaning beyond the schema: that name can narrow either search mode, that state/city/ZIP/name searches sort by SEMS ID while coordinate searches sort by distance, and that paging continues with nextOffset. Enum details for npl_status and coordinate pairings remain primarily in the schema, which is appropriate.

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 and resource (search Superfund/CERCLA/SEMS sites) and states the filter dimensions: location, site name, and NPL status. It also distinguishes itself from the sibling epa_superfund_get_site by routing detailed contaminant lookups there via a returned siteId.

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 clearly explains when to use this search versus epa_superfund_get_site, and gives practical guidance for proximity searches, including narrowing the radius or adding filters if the 50-second deadline is hit. It does not compare against other EPA search tools such as ECHO or TRI, but the primary alternative is explicitly named.

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.