Skip to main content
Glama

Permit history for an address

permit_history_for_address
Read-only

Every known building permit at a street address in any covered area. Costs $0.05 in USDC (x402; Base, Solana, Polygon or Arbitrum); no charge when nothing matches.

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": {
      "address": "<address>"
    },
    "name": "permit_history_for_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo
addressYesStreet address, e.g. 1712 Bluebonnet Ln

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: a $0.05 USDC charge via x402 across four chains, and that nothing is billed when no permits match — details an agent cannot derive from schema or annotations.

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 short sentences, front-loaded with what is returned, followed by the pricing and no-match billing rule. No filler, no repetition of the name or title.

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, the description should say more about what a permit record contains and how many results to expect, and it should flag the zip parameter given the 50% schema coverage. The cost and no-charge-on-empty rule are valuable, but return-shape and parameter roles remain gaps for a paid lookup tool.

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?

Schema coverage is only 50%: address carries an example while zip has just a digit pattern and no description. The description mentions neither parameter, so it does nothing to clarify whether zip is optional narrowing, a required disambiguator, or how partial addresses are handled.

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+resource: retrieving every known building permit at a street address, with the scope qualifier 'in any covered area'. It is distinguishable from count_permits and permit_stats, which aggregate rather than return per-address records, though it never names a sibling explicitly.

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?

There is no explicit when-to-use guidance, no mention of when to prefer search_permits or list_coverage instead, and no note that coverage should be verified first. The phrase 'in any covered area' only hints that coverage varies, leaving the agent to infer routing.

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