Environmental justice screening indicators, pollution burden, and demographic vulnerability
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.9/5 across 5 of 5 tools scored.
The tools are mostly distinct with clear purposes: demographic indicators, county summaries, location-based data, state summaries, and environmental indicators. However, there is some overlap between get_ej_county_summary and get_ej_state_summary in providing EJ data summaries, which could cause mild confusion about which to use for broader regional analysis.
All tool names follow a consistent verb_noun pattern starting with 'get_' followed by descriptive nouns (e.g., get_demographic_indicators, get_ej_county_summary). This uniformity makes the tool set predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose of accessing EPA EJScreen data. Each tool serves a distinct query type (demographic, county, location, state, environmental), providing comprehensive coverage without being overwhelming or sparse.
The tool set covers key aspects of EJScreen data retrieval, including demographic and environmental indicators at various geographic levels. A minor gap exists in lacking tools for more advanced operations like data aggregation or historical trends, but core query needs are well-addressed.
get_demographic_indicatorsInspectGet demographic vulnerability indicators by block group.
Returns demographic data including minority percentage, low income
percentage, linguistic isolation, education levels, and age
distributions. These are the demographic components used in
EJScreen's EJ index calculations.
Args:
state: Two-letter US state abbreviation (e.g. 'WA', 'CA').
county_fips: Optional county FIPS code (3-digit or 5-digit).
If omitted, returns state-level results sorted by
highest demographic index.
limit: Maximum number of block groups to return (default 50, max 500).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | Yes | ||
| county_fips | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_ej_county_summaryInspectGet EJ indicators for census block groups in a county.
Returns EJScreen environmental justice data for block groups within
the specified county, sorted by highest overall environmental burden.
Includes environmental indicators, demographic data, and EJ indexes.
Args:
state: Two-letter US state abbreviation (e.g. 'WA', 'CA').
county_fips: County FIPS code, either 5-digit full (e.g. '53033')
or 3-digit county portion (e.g. '033'). If 3 digits,
state FIPS is prepended automatically.
limit: Maximum number of block groups to return (default 50, max 500).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | Yes | ||
| county_fips | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_ej_data_by_locationInspectGet 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).
| Name | Required | Description | Default |
|---|---|---|---|
| distance | No | ||
| latitude | Yes | ||
| longitude | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_ej_state_summaryInspectGet 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).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_environmental_indicatorsInspectGet specific environmental indicators by block group.
Returns environmental indicator values and state percentiles for
block groups. Can filter to a specific indicator type or return all.
Args:
state: Two-letter US state abbreviation (e.g. 'WA', 'CA').
county_fips: Optional county FIPS code (3-digit or 5-digit).
If omitted, returns state-level results.
indicator: Optional specific indicator to focus on. Options:
'pm25', 'ozone', 'diesel', 'cancer', 'respiratory',
'traffic', 'lead', 'superfund', 'hazwaste',
'wastewater', 'rmp', 'ust'. If omitted, returns all.
limit: Maximum number of block groups to return (default 50, max 500).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | Yes | ||
| indicator | No | ||
| county_fips | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!