Skip to main content
Glama
higherpass

mcp-epa-echo

by higherpass

get_dmr_values

Retrieve actual effluent discharge monitoring report (DMR) values for a facility by NPDES permit or name. Filter by pollutant parameter and date range; specify dates to access historical data beyond the current permit window.

Instructions

Get measured Discharge Monitoring Report (DMR) values for a facility - the actual reported effluent values, not just limits (use get_permit_limits for that).

Identify the facility with npdesId (preferred) or name (resolved internally - ambiguous names return a note asking you to call find_facility first).

THE WINDOWING TRAP, SOLVED: omitting startDate/endDate returns ONLY the facility's CURRENT permit window - which can be as narrow as the last few years, hiding older discharges entirely. The response ALWAYS notes this when no date range is given, even if current-window rows come back. To reach historical discharges (e.g. a pre-2023 permit), pass startDate/endDate (YYYY-MM-DD) - ECHO honors these and returns REAL DATA from the facility's OLDER permit(s), verified live (a 2011-2012 query against a real facility returned 360 real historical report rows). There is no separate historical endpoint to call - passing the date range through to this same tool IS the fix.

If a date range IS given but zero rows come back, the response explains the returned permit window rather than implying "no discharge occurred" - a range outside any permit ECHO has data for looks identical to a genuinely clean period unless you check the window ECHO actually returned.

dmrValue:null with a populated nodiFlag means ECHO recorded a specific reason no value was reported (e.g. monitoring not required that period) - this is NOT the same as a missing/unreported value; nodiFlag:null with dmrValue:null on an overdue report means the value is simply missing. Values may be provisional and subject to revision.

Optionally filter with parameter - matches EITHER an exact parameter code (e.g. "00530") OR a case-insensitive substring of the parameter name (e.g. "suspended"). Results are capped at maxResults (default 50, max 500); when more match, truncated:true and totalMatched show how many were found in total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFacility name, resolved to an NPDES permit internally. Prefer npdesId when you have it - name resolution can match more than one facility.
endDateNoEnd of the DMR date range, YYYY-MM-DD. Requires startDate.
npdesIdNoNPDES permit number (e.g. "GA0038202"). Loosely 2-letter state code + up to 7 alphanumeric characters, but not strictly validated here - pass it exactly as find_facility returned it.
parameterNoPollutant parameter name or code to filter to (e.g. a DMR parameter code). Omit to return all measured parameters.
startDateNoStart of the DMR date range, YYYY-MM-DD. Omitting both startDate and endDate returns only the CURRENT permit window.
maxResultsNo
Behavior5/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. It thoroughly explains key behaviors: the 'windowing trap' with date ranges, handling of zero results, interpretation of null dmrValue with nodiFlag, parameter matching, and result truncation. All behavioral traits are disclosed.

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 well-structured with clear paragraphs and warnings. It is somewhat lengthy but each section adds value with no redundancy. Could be slightly more concise, but overall effective.

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?

Given the complexity (6 parameters, no output schema, no annotations, no siblings), the description is remarkably complete. It covers not only the primary function but edge cases (ambiguous names, zero results, null dmrValue), alternative tools, and behavioral nuances. No gaps identified.

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?

Schema description coverage is high (83%), but the description adds significant meaning beyond the schema: the windowing trap, the interaction between startDate/endDate, the substring matching behavior for parameter, and the meaning of nodiFlag. It adds value, though the schema already documents basics.

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 it gets measured DMR values, not limits, and explicitly distinguishes from get_permit_limits. The verb 'get' and resource 'DMR values' are specific, and the distinction from the sibling is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use (getting actual effluent values) and when-not-to-use (for limits, use get_permit_limits). It also gives detailed guidance on facility identification (prefer npdesId, name resolution with fallback), date range usage, filtering, and result limits.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/higherpass/mcp-epa-echo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server