Skip to main content
Glama

Get one zip code's rental market data

get_zip_market
Read-onlyIdempotent

What does the rental market look like in this zip code? Full profile for a single US zip: rent, cap-rate band (modeled), vacancy, home value, demographics, income, employment, the county's HMDA mortgage lending conditions (purchase/refinance denial rate, median rate and loan, loan-type mix), plus the canonical doorbase.app page URL.

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": {
      "zip": "<zip>"
    },
    "name": "get_zip_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US zip code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the shape of the payload (rent, vacancy, demographics, HMDA lending conditions) and flags that the cap-rate band is 'modeled', which is a meaningful caveat for interpreting results. It does not mention caching/freshness or error behavior for an invalid zip.

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?

Two sentences, front-loaded with a framing question followed by a dense field inventory. Given there is no output schema, the enumeration earns its space, though the list is long enough to be slightly unwieldy.

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?

With no output schema, describing the returned fields is essential and the description does that thoroughly, including the modeled cap-rate caveat. What remains unstated is behavior on an unknown zip or data vintage, which matters for a data-lookup tool but is a minor gap.

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?

The single parameter is fully documented in the schema (100% coverage, with a `^[0-9]{5}$` pattern and '5-digit US zip code' description). The description adds nothing beyond that for `zip`, so the baseline of 3 applies.

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 gives a specific resource ('Full profile for a single US zip') and enumerates the exact data domains returned, which makes it clearly distinct from siblings like compare_zips (multi-zip) and rent_trend (time series). It never names those siblings explicitly, so differentiation is inferred from the 'single zip / full profile' framing rather than stated.

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 opening question ('What does the rental market look like in this zip code?') implies the use case of pulling a one-zip snapshot, but there is no explicit 'use this when' guidance, no exclusions, and no pointer to compare_zips or search_markets for the multi-zip or discovery cases.

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