EPA EJScreen

get_ej_state_summary

Get a state-level overview of EJ indicators across block groups.

Returns the most environmentally burdened block groups in the state,
sorted by PM2.5 percentile. Useful for identifying areas with the
highest environmental justice concerns.

Args:
    state: Two-letter US state abbreviation (e.g. 'WA', 'CA').
    limit: Maximum number of block groups to return (default 100, max 500).

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": {
      "state": "<state>"
    },
    "name": "get_ej_state_summary"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`state`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description bears responsibility. It discloses that the tool returns 'most environmentally burdened block groups' and that results are 'sorted by PM2.5 percentile,' which is meaningful behavior beyond the schema. It does not discuss error handling or output shape, but the output schema covers return details.

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?

Three concise sentences plus a compact Args list; no filler. The tool's purpose and key parameters are front-loaded.

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?

The tool is simple (2 params, 1 required), and an output schema exists. The description covers the essential behavior, sorting, and parameter constraints, making it sufficient. It could add a note about if no state match, but not necessary.

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?

The Args section explains both parameters: 'state' requires a two-letter abbreviation with examples, and 'limit' specifies maximum block groups with default 100 and max 500. The schema only provides type/default, so this is high-value semantic detail.

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 starts with 'Get a state-level overview of EJ indicators across block groups' and specifies output: 'most environmentally burdened block groups... sorted by PM2.5 percentile.' This clearly distinguishes from siblings such as get_ej_county_summary and get_ej_data_by_location.

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 states the tool is 'Useful for identifying areas with the highest environmental justice concerns,' providing clear context. It does not explicitly name alternatives or exclusions, but the state-level framing plus sibling names make the intended scope apparent.

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?