Skip to main content
Glama

perchpermits/nashville-building-permits

perchpermits--nashville-building-permits
Destructive

This tool calls the Actor "perchpermits/nashville-building-permits" and retrieves its output results. Actor description: Davidson County TN permits and applications, joined to the licensed contractor, property owner, sub-trade permits, and inspection stage. Pay per record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo`search` returns one row per permit. `contractors` returns one row per contractor, ranked by permit count and valuation across the matching permits. Example values: "search"search
zipsNoRestrict to these ZIP codes.
scopeNoPreset classifier applied to the permit type, subtype, and description. Presets strip boilerplate (for example 'not to add a second kitchen') before matching. Example values: "any"any
dateToNoISO date (YYYY-MM-DD), inclusive. Defaults to today.
enrichNoJoin each permit to Metro ePermits: licensed contractor (name, license, phone), property owner, required sub-trade permits with satisfied/outstanding status, and inspection stage. About one second per permit, politely rate-limited. Billed as `enriched-permit` instead of `permit`.
parcelNoExact Davidson County parcel ID, e.g. `08309024300`.
addressNoSubstring of the street address, e.g. `1234 WOODLAND ST`. Metro stores addresses upper-case without unit numbers.
keywordNoFree-text substring matched against the permit description on the server (case-insensitive). Combine with a scope or use alone.
datasetsNo`issued` = permits already issued (date filter applies to issue date). `applications` = filed but not yet issued, an early signal (date filter applies to filing date). `both` merges them. Example values: "both"both
dateFromNoISO date (YYYY-MM-DD). Defaults to 90 days ago when no other narrowing filter is given.
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
applicantNoSubstring of the applicant / contact on the open dataset (the paperwork filer, often the contractor).
maxRecordsNoCap on rows returned (permits in search mode, contractors in contractors mode). Example values: 200
minPermitsNoContractors mode only: hide contractors with fewer matching permits than this. Example values: 1
permitTypeNoSubstring of Metro's permit type or subtype description, e.g. `Residential - Rehab`, `Swimming Pool`, `Demolition`.
maxValuationNoOnly permits with a declared construction cost at or below this amount.
minValuationNoOnly permits with a declared construction cost at or above this amount.
permitNumberNoExact permit number, e.g. `2026045225`. Use with `enrich` for a full case lookup.
residentialOnlyNoDrop permits whose type or description reads as commercial.
enrichMaxAgeDaysNoEnrichment fetched more recently than this is served from cache instead of re-querying ePermits. Set 0 to always refetch. Example values: 7
maxPermitsScannedNoContractors mode only: how many matching permits (newest first) feed the ranking. Not billed; only the contractor rows are. Example values: 2000

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior1/5

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

The description says 'retrieves its output results,' implying a read-only operation, while annotations declare readOnlyHint=false and destructiveHint=true. This is a direct contradiction; the description fails to disclose any destructive or side-effecting behavior, and actually undercuts the annotation.

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?

The description is two sentences with no filler. The first sentence clearly states the action, and the second gives the actor's purpose. It is appropriately sized for the information it conveys.

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

Completeness2/5

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

Given the tool has 21 parameters, multiple modes (search/contractors), enrichment options, and a rich output schema, the description is too minimal. It fails to mention the two modes, the optional enrichment, or that it can rank contractors. The contradiction with annotations is a critical omission, making the overall context incomplete.

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%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides; it simply names the actor. It does not compensate for any gaps, but none exist in 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?

The description clearly states the tool calls the Actor 'perchpermits/nashville-building-permits' and retrieves its output, with a specific actor description of Nashville building permits data. It is specific about the verb and resource, but does not explicitly differentiate from sibling tools beyond the unique 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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only extra hint is 'Pay per record,' which is not a usage guideline. Sibling tools are not mentioned.

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.