Skip to main content
Glama

Marden Yard Permits

search_permits

Permits by area (jurisdiction, ZIP, community area), trade, minimum permit-declared value, date range and confidence floor, with a short brief.

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

NameRequiredDescriptionDefault
toNoIssued on or before, YYYY-MM-DD
zipNo5-digit site ZIP (not available for Chicago)
daysNoIssued in the last N days (default 7; anonymous max 7)
fromNoIssued on or after, YYYY-MM-DD
limitNoMax rows (anonymous 5, keyed 50)
tradeNo
min_valueNoMinimum permit-declared value; only permits with a reliable value match
jurisdictionNoJurisdiction slug: chicago, austin, los-angeles, seattle
community_areaNoChicago community area number
min_confidenceNoTrade confidence floor, 0-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire disclosure burden, and it says nothing about read-only safety, auth/anonymous tiering, result caps, or ordering. 'With a short brief' is the only behavioral hint about output shape, and it is left unexplained.

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 dense sentence, front-loaded with the resource and its filter axes, no filler or marketing language. It borders on a list dump, but every clause maps to real parameters.

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?

For a 10-parameter, zero-required tool with no annotations and no output schema, the definition is minimal but not wrong. It omits what happens with no filters (default 7 days is only visible in the schema), how results are ordered or capped, and what the 'brief' contains.

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 90%, so the schema already documents each of the 10 parameters in detail; the description largely restates those same axes. It does consolidate the three geo filters under 'area' and correctly pairs min_value with permit-declared value, but adds no format or defaulting detail 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?

Names a concrete resource (permits) and enumerates the axes it filters on — area (jurisdiction, ZIP, community area), trade, value, date range, confidence — plus the promise of a 'short brief'. That is specific enough to separate it from permit_detail, but it never explicitly frames the verb as 'search/list matching permits' or contrasts with the siblings by name.

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 statement of when to reach for this versus permit_detail, coverage, or watch_area, and no preconditions (API key level, defaults) are given. Usage is only inferable from the filter list; an agent must guess that this is the bulk-discovery path and permit_detail the per-record path.

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