Skip to main content
Glama

NPDES Permit Renewal Sentinel

NPDES permit renewal: free sample

npdes_permit_example
Read-onlyIdempotent

Free sample: a real answer, same shape as npdes_permit_lookup.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "npdes_permit_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful behavioral facts not in annotations: the call is free (no cost) and the response shape mirrors npdes_permit_lookup. However, "a real answer" is confusing for a tool labeled a sample – it never clarifies whether the underlying data is illustrative or live, which is the one behavioral question an agent most needs answered here.

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?

A single short sentence with no padding, and the key qualifier ("free sample") is front-loaded. It is efficient but thin to the point of under-specification, so it earns credit for brevity rather than for informative density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need not be explained, and zero parameters keep the surface simple. But the description omits the two things an agent still needs: what kind of content the sample contains and whether it is safe to use as real permit information. For a tool whose entire value proposition is being a sample, that gap matters.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No parameter claims are made that could mislead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Free sample" plus "a real answer" is marketing framing rather than a statement of what the tool returns; it never says the output is an NPDES permit renewal example record. The only concrete signal is a pointer to a sibling's output shape, which is a format hint, not a purpose. An agent cannot tell from this text what it will actually get back.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and the sibling npdes_permit_lookup is referenced only as a shape reference, not as an alternative to prefer for real queries. The word "sample" weakly implies trial/demo use, but that inference is left entirely to the reader. No prerequisites, no exclusions.

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.