Skip to main content
Glama

Marden Yard Permits

coverage

Which jurisdictions are covered, how fresh each is, and approximate weekly permit volume.

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
jurisdictionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal the shape of the response (jurisdictions, freshness, weekly volume), which is genuinely useful, but says nothing about permissions, whether results are paged or capped, or what 'approximate' means in practice.

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?

One front-loaded sentence with no filler, though the fragmentary phrasing ('Which jurisdictions are covered...') reads as a question rather than a statement of what the tool does. Every word earns its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only source of return-value information, and it does cover the three returned fields. What it omits is the behavior of the sole parameter and any note on result size or scope, which for a discovery tool is a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one optional 'jurisdiction' parameter with 0% schema description coverage, and the description never explains it. An agent cannot tell from the text whether passing it narrows the result to a single jurisdiction or whether the tool always returns the full coverage list. That gap directly affects correct invocation.

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

Purpose4/5

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

The description names the resource precisely: jurisdictions, their data freshness, and approximate weekly permit volume. That is a specific read-oriented purpose that the bare name 'coverage' does not convey on its own. It does not explicitly contrast itself with permit_detail or search_permits, so sibling differentiation comes only from the resource it returns.

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

Usage Guidelines3/5

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

The use case is only implied: an agent can infer that the tool answers 'what regions are supported and how current is the data,' which is useful before calling search_permits. There is no explicit when-to-use or when-not guidance, and no alternative is named.

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.

Resources