EPA EJScreen

get_ej_data_by_location

Get EJScreen environmental justice data for a specific location.

Uses the EPA EJScreen REST broker to retrieve EJ screening indicators
for a point location with a buffer distance. Returns environmental
indicators, demographic data, and EJ indexes.

Args:
    latitude: Latitude of the location (e.g. 47.61).
    longitude: Longitude of the location (e.g. -122.33).
    distance: Buffer distance in miles around the point (default 1.0).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_ej_data_by_location"
  }
}

Input Schema

Name	Required	Description	Default
`distance`	No
`latitude`	Yes
`longitude`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the EPA EJScreen REST broker and the types of data returned, but does not disclose limitations, error handling, rate limits, or any side effects (though the operation appears read-only from 'Get' and 'retrieve'). This is adequate but not rich.

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 concise and well-organized: a clear one-sentence purpose, a brief implementation/context sentence, a return summary, and a structured parameter list. The REST broker detail is useful context and does not seem wasteful.

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?

Given the tool's moderate complexity and the presence of an output schema (which covers return details), the description provides sufficient context: purpose, parameter semantics, and a high-level summary of returned data. It does not need to explain return values in depth. The only gap is lack of explicit alternative tool guidance.

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 description coverage is 0%, but the description provides a full Args section with examples and defaults for all three parameters (latitude, longitude, distance). This adds clear meaning beyond the bare schema and fully compensates for the missing schema descriptions.

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's purpose: 'Get EJScreen environmental justice data for a specific location' with specifics about point location and buffer distance. It distinguishes from siblings like county/state summary tools by emphasizing point-based location and returning combined environmental, demographic, and EJ index data.

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?

The description implies usage for point-based queries ('for a point location with a buffer distance') but does not explicitly mention alternatives or when not to use this tool. Sibling tools (e.g., get_ej_county_summary) are not referenced, so the guidance is inferred rather than explicit.

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

All EPA EJScreen 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.

Resources

Need Help?