Skip to main content
Glama

Weekly permit report

weekly_permit_report
Read-only

All building permits issued in the last 7 days for one area, with counts by category. Costs $1.00 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": {
      "jurisdiction": "<jurisdiction>"
    },
    "name": "weekly_permit_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoPermit category, e.g. roof, pool, solar, hvac, new_residential
jurisdictionYesArea id, e.g. new-york-ny, miami-dade-fl. Use list_coverage for names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's main added value is the pricing model: $1.00 USDC via x402 on four named chains, plus the explicit 'no charge when nothing matches' guarantee. That is real behavioral context an agent would otherwise not have. It stops short of describing response shape or how a category filter interacts with the counts.

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 compact clauses: scope first, pricing second. No filler, and the most decision-relevant facts (time window, cost, free-on-empty) are front-loaded.

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?

For a two-parameter read-only report with full schema coverage and no output schema, the definition covers purpose, cost, and the empty-result billing edge case. The remaining gap is the exact response structure, which a paid tool arguably should preview since the agent commits money before seeing the output.

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 coverage is 100% and both parameters are enumerated with descriptions, so the schema carries the semantics. The description adds only the 'one area' framing and the 'counts by category' output hint, and leaves ambiguous whether passing a category filters the result set or just narrows the breakdown.

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 ('All building permits issued in the last 7 days for one area') plus the return shape ('counts by category'). The fixed 7-day window and single-area scope distinguish it from count_permits and permit_trends, though no sibling is named explicitly.

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 fixed 7-day/per-area scope implies when this is appropriate, but there is no explicit when-to-use guidance and no routing to alternatives such as permit_stats for aggregates or permit_trends for longer horizons. An agent must infer the boundary from the time window alone.

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