Skip to main content
Glama

NPDES Permit Renewal Sentinel

NPDES permit renewal lookup

npdes_permit_lookup
Read-onlyIdempotent

Use this when you need the renewal deadline of a US water discharge permit: for 1 to 10 NPDES permit numbers, the expiration date on file with EPA, the last day to send the renewal application (180 days before expiration, and the safe date one day earlier), whether that date binds (EPA-issued permit) or the State's own rule governs, days left, and the published status once the term has ended. Individual permits only. No facility names, no addresses. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

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": {
      "permits": "<permits>"
    },
    "name": "npdes_permit_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
permitsYes1 to 10 NPDES permit numbers (9 ASCII letters or digits each, for example NH0100013), comma-separated
free_trialNoSet to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.

Output Schema

NameRequiredDescriptionDefault
dataNoThe source data: what it is, its date, when it was downloaded, and the fields used
noteNoHow to read the deadline fields of each result
rulesNoThe rules read at the source, each with its id, url and whether it was applied
licenceNoThe license under which the source data is published
resultsNoOne entry per permit number, in input order
conflictsNoThe official texts that disagree, each flagged by name
disclaimerNoInformation only, not legal advice, and not affiliated with any agency
consequencesNoWhat the cited law says of discharging without a permit in force, with its references

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnly/idempotent/non-destructive/openWorld; the description adds substantial behavioral context the annotations cannot: a per-call price of 0.01 USDC via x402, the fact that payment is required unless free_trial is set, and a concrete free-trial quota (3 calls per day per caller, shared with the web route, under a service-wide daily cap). It also discloses the underlying business rule (180 days before expiration, safe date one day earlier) and the EPA-versus-State determination, which tells the agent what the returned dates actually mean.

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?

Everything is front-loaded: the use case first, then outputs, then scope limits, then pricing. Every clause carries information, but it is delivered as one long multi-clause sentence mixing return fields, eligibility rules, and billing, which would read faster as short segments.

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?

For a read-only lookup with an output schema and full parameter documentation, the description covers the remaining gaps an agent needs: scope limits, cost and payment mechanism, free-trial behavior, and the definition of the dates returned. Nothing required to invoke it correctly is missing.

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% and both parameters are already documented, including the 9-character format and the free-trial semantics, so the baseline is 3. The description restates the 1-to-10 permit count and free-trial behavior without adding format or edge-case detail beyond the schema (e.g., what happens for invalid or unknown permit numbers).

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 opens with a concrete verb-and-resource (renewal deadline of a US water discharge permit) and enumerates exactly what comes back: expiration date, last day to send renewal, the 180-day rule, whether EPA or State rule binds, days left, and post-term status. It also draws a hard scope line ('Individual permits only. No facility names, no addresses.'), so an agent can tell what this tool will and will not answer without opening the schema.

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?

'Use this when you need the renewal deadline' gives an explicit triggering condition, and 'Individual permits only' excludes general permits. It does not reference the sibling npdes_permit_example or any other alternative, so an agent gets a clear use case but no routing comparison.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.