Permit Scouter

Search permits

search_permits

Read-onlyIdempotent

Search new building permits by trade, job value, date, zip or city. Newest first, up to 25 per call. Price: $0.02 per call (x402, USDC on Base).

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

Input Schema

Name	Required	Description
`q`	No	Words in the work description, e.g. heat pump
`zip`	No	5-digit zip code
`city`	No	City name, e.g. TAMPA
`limit`	No	Results per call, 1 to 25
`since`	No	Filed on or after, YYYY-MM-DD
`trade`	No	One of: roofing, hvac, solar, pool, electrical, plumbing, windows_doors, new_construction, remodel, demolition
`until`	No	Filed on or before, YYYY-MM-DD
`offset`	No	Start position for paging
`min_value`	No	Minimum job value in US dollars
`jurisdiction`	No	Source key from coverage, e.g. tampa

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: results are newest-first, capped at 25 per call, and each call costs $0.02 via x402/USDC on Base — a paid-call disclosure an agent must know before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler; the search scope is front-loaded and the operational constraints (ordering, page size, price) follow. Every clause earns its place.

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?

With no output schema, the description usefully covers result ordering and page size, and it discloses the payment model. It does not mention paging mechanics despite an offset param, but for a 10-param, all-optional search this is close to complete.

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%, with each of the 10 params documented including the trade enum values and date format, so the baseline is 3. The description restates filter categories (trade, job value, date, zip, city) but adds no syntax, defaults, or interaction rules beyond the schema.

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?

States a specific verb and resource ('Search new building permits') plus the filterable dimensions (trade, job value, date, zip, city). It is clearly distinguishable from a single-record fetch like get_permit, but it never names or contrasts with the actual siblings (sample_permits, coverage, contractor_history).

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 guidance on when to use this instead of sample_permits (free preview?) or get_permit (single record) or coverage. The description implies a filtered list search but never states prerequisites, exclusions, or the alternative that should be chosen in other cases.

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

All Permit Scouter 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?