Drinking Water — EPA SDWIS: Systems, Violations, Lead & Copper, PFAS (UCMR5)

get_current_health_violations

Read-only

List current (unresolved) health-based drinking water violations from EPA SDWIS: maximum contaminant level (MCL), maximum residual disinfectant level (MRDL), and treatment-technique violations whose status is Unaddressed or Addressed. Monitoring and reporting violations are excluded. Filter by state, by PWSID, or by contaminant code; most recent compliance periods first.

Input Schema

Name	Required	Description
`limit`	No	Max results (default 50, max 500)
`pwsid`	No	Only this system's violations
`state`	No	Two-letter state code, e.g. IL
`contaminant_code`	No	SDWIS contaminant code, e.g. 1040 (nitrate)

Output Schema

Name	Required	Description	Default
`data`	Yes
`status`	Yes
`provenance`	Yes
`status_detail`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "anyOf": [
+        {
+          "properties": {
+            "count": {
+              "type": "integer"
+            },
+            "violations": {
+              "items": {
+                "properties": {
+                  "category": {
+                    "type": "string"
+                  },
+                  "compliance_period_begin": {
+                    "type": "string"
+                  },
+                  "compliance_period_end": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "contaminant": {
+                    "type": "string"
+                  },
+                  "contaminant_code": {
+                    "type": "string"
+                  },
+                  "federal_mcl": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "first_reported": {
+                    "type": "string"
+                  },
+                  "is_major": {
+                    "type": "boolean"
+                  },
+                  "last_reported": {
+                    "type": "string"
+                  },
+                  "measure": {
+                    "type": [
+                      "number",
+                      "null"
+                    ]
+                  },
+                  "pwsid": {
+                    "type": "string"
+                  },
+                  "rule": {
+                    "type": "string"
+                  },
+                  "state_mcl": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "status": {
+                    "type": "string"
+                  },
+                  "system_name": {
+                    "type": "string"
+                  },
+                  "system_state": {
+                    "type": "string"
+                  },
+                  "unit": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "violation_id": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "count",
+            "violations"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "provenance": {
+      "properties": {
+        "as_of": {
+          "type": "string"
+        },
+        "cadence": {
+          "type": "string"
+        },
+        "cadence_detail": {
+          "type": "string"
+        },
+        "fetched_at": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "source_detail": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "as_of",
+        "cadence",
+        "cadence_detail",
+        "fetched_at",
+        "source",
+        "source_detail"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "no_data",
+        "source_unavailable",
+        "withheld"
+      ],
+      "type": "string"
+    },
+    "status_detail": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "data",
+    "provenance"
+  ],
+  "type": "object"
+}

First observedNov 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the implicit status filter, the excluded violation classes, and the default sort ('most recent compliance periods first'), which an agent could not infer from annotations alone.

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?

Every sentence carries information: definition, included categories, excluded categories, filter dimensions, sort order. The opening sentence front-loads the core purpose. Slightly dense with the parenthetical acronym list, but no filler.

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?

An output schema exists, so return-shape explanation is unnecessary; the description still covers scope, filtering axes, and ordering, which is what an agent needs to call it correctly. Minor residual gap: nothing about how the limit interacts with ordering or what happens when no filters are supplied.

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 description coverage is 100%, so all four parameters (limit, pwsid, state, contaminant_code) are already documented with examples. The description restates the three filter dimensions but adds no syntax, format, or combination semantics beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource (list current unresolved drinking water violations from EPA SDWIS) and then enumerates the exact violation categories included (MCL, MRDL, treatment-technique) and excluded (monitoring and reporting). That level of scope precision clearly separates it from siblings like list_contaminants_with_violations and the state/county summary tools.

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 concrete entry conditions: filter by state, by PWSID, or by contaminant code, plus the status filter is pre-applied (Unaddressed or Addressed only). It also states what is excluded, which prevents misuse. It does not explicitly name an alternative sibling for the adjacent questions (e.g., 'use list_contaminants_with_violations for a roll-up'), so it stops short of a 5.

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

All Drinking Water — EPA SDWIS: Systems, Violations, Lead & Copper, PFAS (UCMR5) 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?