epa-mcp-server

Get EJScreen Environmental Justice Indicators

epa_ejscreen_get_scores

Read-onlyIdempotent

EJScreen: Get EJScreen environmental-justice indicators for a point and surrounding buffer. Returns the 13 EJScreen environmental indicators (PM2.5, ozone, diesel particulate, NO2, lead paint, traffic proximity, Superfund/RMP/hazardous-waste/wastewater proximity, underground storage tanks, drinking-water non-compliance, and RSEI toxic air releases) and 6 demographic indicators (people of color, low income, limited English, less than high school, under 5, over 64), each with national and state percentiles plus EJ Index values, along with the Demographic Index and Supplemental Demographic Index. Data is EJScreen v2.2 (2022) served via the community-maintained EJAM API (api.ejanalysis.com, Public Environmental Data Partners), which rehosts EJScreen after EPA discontinued public access in 2025 — not a live EPA endpoint. Provide latitude, longitude, and a buffer distance (default 1 mile, max 15 miles). Points outside US coverage return a coverage note instead of indicators.

Input Schema

Name	Required	Description	Default
`unit`	No	Unit for distance. Kilometers are converted to miles (× 0.621371) before the request.	miles
`distance`	No	Buffer radius around the point, in the given unit (default 1). The miles-equivalent must be 15 or less.
`latitude`	Yes	Latitude in decimal degrees.
`longitude`	Yes	Longitude in decimal degrees.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Guidance when the point is outside EJScreen coverage and no indicators were returned.
`coverage`	No	Whether EJScreen data was available for the point.
`location`	No	The queried location and buffer context.
`reportUrl`	No	Link (absolute URL) to the full EJScreen report for this point and buffer.
`dataSource`	No	Provenance and vintage of the data.
`demographic`	No	EJScreen demographic indicators present for the area. Empty when out of coverage.
`environmental`	No	EJScreen environmental indicators present for the area. Empty when out of coverage.
`demographicIndex`	No	EJScreen Demographic Index. Absent when out of coverage.
`supplementalDemographicIndex`	No	EJScreen Supplemental Demographic Index. Absent when out of coverage.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial context beyond the readOnly/idempotent/openWorld hints: the exact data vintage (EJScreen v2.2, 2022), the serving path (community-maintained EJAM API, not a live EPA endpoint after 2025 discontinuation), and the out-of-coverage response behavior. This is exactly the provenance an agent needs to judge trustworthiness and failure modes.

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?

Placeholder — see justification text in the conciseness_structure field of the final assessment.

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?

With an output schema, 100% parameter coverage and annotations already present, the remaining burden is provenance and edge-case behavior — both covered (EJAM rehosting caveat, US-coverage fallback, buffer cap). Nothing needed to call it correctly is missing.

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%, with unit conversion, buffer bounds and degree ranges all documented in the schema itself. The description restates the default and the 15-mile ceiling but adds no format or interpretation detail beyond that, so the baseline 3 applies.

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?

Names a specific verb and resource (EJScreen environmental-justice indicators) scoped to 'a point and surrounding buffer', which cleanly separates it from the sibling tools that cover air quality, facilities, violations, TRI releases and water systems. The indicator families named confirm what the agent gets back.

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 clear usage context — supply latitude, longitude and a buffer distance (default 1 mile, max 15 miles) — and states the US-only boundary condition with a stated fallback ('coverage note'). It does not name an alternative tool for non-point or non-US queries, so it stops short of explicit when-not guidance.

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

All epa-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.