Skip to main content
Glama

Search US rental markets by zip

search_markets
Read-onlyIdempotent

Which US zip codes match these rental-market criteria? Filters 30,000+ US zip codes by state, cap rate, vacancy, rent, population, home value, and renter share. Returns matching zips with key investor metrics and a doorbase.app link for each. Cap rates are a modeled band; min_cap_rate matches the band's high end.

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_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNo2-letter US state code, e.g. GA. Omit for nationwide.
sort_byNocap_rate
min_cap_rateNoMinimum estimated cap rate in percent; matches cap_rate_high (band top) >= value.
min_populationNoMinimum zip population.
max_median_rentNoMaximum median monthly rent in USD.
min_median_rentNoMinimum median monthly rent in USD.
max_vacancy_rateNoMaximum vacancy rate in percent.
min_renter_ratioNoMinimum renter-occupied share in percent.
max_median_home_valueNoMaximum median home value in USD.

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 establish this as a safe, read-only, idempotent operation. The description adds useful behavioral context: it searches 30,000+ zips, returns investor metrics plus a doorbase.app link, and explains that cap rates are modeled bands with min_cap_rate matching the band's high end.

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 front-loaded with the core question, then packs filtering scope, return contents, and the cap-rate edge case into compact sentences. Every sentence contributes useful information without repetition.

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 10-parameter search tool with no output schema, the description sufficiently explains the searchable dimensions and the nature of returned results. It omits minor operational details like limit enforcement and sort behavior, but those are covered by the schema and annotations.

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 coverage is 80%, so the baseline is 3. The description adds value by grouping the major filter dimensions and specifically clarifying the modeled-band semantics for min_cap_rate, though it does not cover sort_by or limit behavior beyond what the schema already states.

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 a specific action and resource: filtering US zip codes by rental-market criteria and returning matches. It does not explicitly distinguish itself from siblings like get_zip_market, compare_zips, or top_markets, but the search/filter scope is evident.

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?

It implies the tool is used to find zips matching criteria, but gives no explicit guidance on when to choose it over compare_zips, get_zip_market, top_markets, or rent_trend. There are no exclusions or alternative-routing instructions.

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