Skip to main content
Glama

dealcheck: US property deal-check

nashville_deal_check

Read-only

Deprecated: use ziplot_deal_check. Public-record due-diligence facts for a US residential address. Any US address: FEMA flood zone at the geocoded point, HUD FY2026 Small Area FMR (or area FMR) by bedrooms, and a property-tax estimate: official rates in Nashville (Metro rate), Denver (levy by tax district), Chicago (Cook County tax code) and Maricopa County cities (tax area code), elsewhere a rough county-level estimate from Census ACS, labeled as such. Zoning or address-level eligibility plus short-term-rental (STR) rules (coverage level "full"): Nashville / Davidson County, TN; Denver (City and County), CO; Scottsdale (city limits), AZ; Chicago (city limits), IL; New York City (five boroughs), NY; Austin (full- and limited-purpose city), TX; Boise (City of Boise and unincorporated Ada County), ID; Miami (City of Miami, Miami Beach, unincorporated Miami-Dade), FL; Orlando (City of Orlando and unincorporated Orange County), FL; San Diego (City of San Diego), CA. City-wide STR rules plus an address-level permit lookup ("partial"): Phoenix (city limits), AZ; Tempe (city limits), AZ. 59 more cities, counties and resort areas get STR rules and taxes only, with no zoning or per-address check ("rules_only"). The current market list with levels and verified dates: GET /v1/coverage; str.granularity in each answer says which applies. Elsewhere zoning/STR return not_covered. Every value carries a source and as-of date. HOA/deed restrictions are not checked. Informational only; not legal/tax/insurance/lending advice. Ziplot tool (original name kept for compatibility; ziplot_deal_check is the same tool). Status values. Top-level status: ok = every evaluated section answered; needs_review = partial answer, at least one section needs a person or a retry (read each section's status and the warnings); unavailable = no section could be answered (address not found, or every source failed); out_of_scope = no evaluated section applies at this address. Section status uses the same words plus not_covered (this area is not evaluated). str.status follows the two permit determinations: new_non_owner_occupied_permit.value (allowed, not_allowed, needs_review, out_of_scope, not_covered, unavailable) and owner_occupied_permit.value (possible, not_allowed, needs_review, out_of_scope, not_covered, unavailable). Both firm = ok, one firm and one not = needs_review, none usable = unavailable. Exception: an owner_occupied_permit of possible that rests only on an active city STR license (owner_occupied_permit.basis.kind active_city_license, Denver and Scottsdale) is not a firm yes, so str.status stays needs_review there. str.supporting_data_status appears when side lookups such as permit counts or building lists were incomplete.

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

Input Schema

NameRequiredDescriptionDefault
valueNoOptional purchase price or value in USD. Echoed in query.value. Where no Assessor value exists it drives property_tax.estimated_annual_tax; where one exists, the estimate at your value is in property_tax.estimate_at_your_value.
addressYesUS street address including city and state, e.g. '321 50th Ave N, Nashville, TN'
includeNoOptional sections to return. Omit it (or send an empty list) for all five; 'zoning' adds the zoning lookup used by the STR section.
bedroomsNoFor HUD rent benchmark. Defaults to 2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / include / default
      Added value: +[
      +  "rent",
      +  "tax",
      +  "flood",
      +  "str",
      +  "zoning"
      +]
    • addedInput schema / properties / include / description
      Added value: +"Optional sections to return. Omit it (or send an empty list) for all five; 'zoning' adds the zoning lookup used by the STR section."
    • addedInput schema / properties / include / items / type
      Added value: +"string"
  2. Changed1 schema field changed
    • changedInput schema / properties / value / description
      Previous value: -"Optional purchase price or value in USD. Used for the county-rate tax estimate where no parcel value is available."New value: +"Optional purchase price or value in USD. Echoed in query.value. Where no Assessor value exists it drives property_tax.estimated_annual_tax; where one exists, the estimate at your value is in property_tax.estimate_at_your_value."
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description does not contradict them. It adds substantial behavioral context the annotations cannot express: the three-tier coverage model, per-source 'as-of date' labeling, the 'rough county-level estimate ... labeled as such' caveat, and the disclaimer that results are informational only. However, the bulk of the text is a response-taxonomy dump (status values, str.status combination rules) rather than disclosure of operational behavior such as latency, rate limits, or failure modes.

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

Conciseness2/5

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

The deprecation warning is correctly front-loaded, but the body is a single run-on block of roughly 350 words with long enumerations of cities and counties and a full status-state taxonomy. It also restates itself: the name-compatibility note ('Ziplot tool (original name kept for compatibility; ziplot_deal_check is the same tool)') duplicates the opening sentence, and 'Section status uses the same words plus not_covered' adds little. The vocabulary is dense but the structure buries actionable guidance under coverage lists an agent cannot practically act on.

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

Completeness5/5

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

There is no output schema, so the description must carry the full burden of explaining returns, and it does: status semantics for top-level, section and str-level results, the exception for owner_occupied_permit.basis.kind=active_city_license in Denver and Scottsdale, and where supporting_data_status appears. For a tool with four optional parameters, multiple coverage tiers and no output contract, this is complete enough that an agent would not need to guess at result interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 and the schema already explains value, address, include and bedrooms. The description still adds meaning the schema does not: it clarifies that coverage is address-dependent ('Elsewhere zoning/STR return not_covered', 'str.granularity in each answer says which applies'), which directly informs how the address string and the include list will behave for a given location. That address-drives-coverage insight is the real value-add beyond the schema's field-by-field wording.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with an explicit deprecation routing ('Deprecated: use ziplot_deal_check') and then states a specific resource and scope: public-record due-diligence facts for any US residential address covering flood zone, HUD FMR, property tax, zoning and STR rules. It also explicitly resolves the sibling relationship ('ziplot_deal_check is the same tool'), so an agent can distinguish it from ziplot_deal_check and ziplot_deal_picture without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use-this-instead directive pointing at ziplot_deal_check, plus scope boundaries: 'HOA/deed restrictions are not checked', 'Informational only; not legal/tax/insurance/lending advice', and explicit coverage tiers (full / partial / rules_only / not_covered) that tell the agent when the zoning and STR sections will actually return data. The deprecation instruction is front-loaded rather than buried.

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