Basinwise

Does this state need a credentialed plan preparer?

get_credential_gate

Read-onlyIdempotent

Whether a state requires a credentialed preparer (California's Qualified SWPPP Developer, and the analogous credential elsewhere) to prepare or sign a stormwater pollution prevention plan, and whether that requirement bites for a site of this size. This is the answer that decides whether a generated document is the operator's deliverable or a DRAFT for a credentialed person to review and sign, so documentStatus states that consequence in plain language on every response. gate is "open", "gated", "conditional" or "unknown"; a state we have not verified returns "unknown" and must never be treated as open. appliesToThisSite is null when the trigger is an acreage threshold you did not give acres for, or a plan-scope test we cannot resolve from site facts. Free, no API key needed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`acres`	No	Acres disturbed. Optional but worth sending: several states gate only above an acreage threshold, and without it a conditional state can only name the threshold rather than resolve it.
`state`	Yes	Two-letter state, territory or DC code, e.g. "CA".

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds transparency about cost ('Free, no API key needed'), behavioral rules for unknown states, and consequences for document status. This goes well beyond what annotations provide.

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 moderately long but well-structured, starting with the core question, then detailing output semantics and edge cases. Every sentence adds information, though a slightly tighter focus could improve efficiency.

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?

Without an output schema, the description fully explains return fields (gate, appliesToThisSite, documentStatus) and their meanings. It addresses edge cases (unknown states, null appliesToThisSite) and provides practical usage notes. Complete for a simple query tool.

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 coverage is 100% with descriptions for both parameters. The description adds context, especially for the 'acres' parameter, explaining its optionality and practical significance for resolving thresholds. This adds value beyond the schema.

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 title and description clearly state the tool answers whether a state requires a credentialed plan preparer. It distinguishes itself from siblings like determine_permit, get_requirements, get_usage, and list_jurisdictions by focusing on the credential gate, a unique function.

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?

The description explains the tool's purpose and the meaning of its outputs ('gate', 'appliesToThisSite', 'documentStatus'), including the critical warning that 'unknown' must never be treated as open. It does not explicitly contrast with alternatives, but the function is distinct enough.

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

All Basinwise tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: permit determination, credential gate check, requirements retrieval, usage info, and jurisdiction listing. No overlaps or confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., determine_permit, get_usage, list_jurisdictions), making them predictable and readable.

Tool Count5/5

With 5 tools, the server is well-scoped for its domain of NPDES permit compliance, covering essential operations without unnecessary bloat.

Completeness4/5

The set covers permit determination, requirements, credential gates, jurisdiction info, and usage—leaving minor gaps like direct document submission or status tracking, but core workflows are well-supported.

Resources

Need Help?