Skip to main content
Glama

Realtors Dashboard

Search U.S. housing markets

search_housing_markets
Read-onlyIdempotent

Search the published 50-state and DC dataset by state, county, Census place, or ZIP. Filter or sort on asking price or Census owner-reported value. Use a geography level to enumerate its records.

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

Input Schema

NameRequiredDescriptionDefault
qNoLocation, for example Springfield, MA or 02108
maxNoPrice in US dollars
minNoPrice in US dollars
pageNoResult page, starting at 1
sortNoOrdering
levelNoGeography
limitNoMaximum records to return
stateNoTwo-letter USPS state or DC abbreviation
metricNoPrice filter basis

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds only that results are drawn from a 'published' dataset with 'Census owner-reported' values, which is useful provenance but not much beyond the annotations; pagination, result shape, and empty-result behavior are left unstated.

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?

Three short sentences with no filler, and the dataset scope is front-loaded. The final sentence ('Use a geography level to enumerate its records') is slightly opaque about what enumeration means in practice, which keeps it from a 5.

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 nine-parameter search tool with no output schema, the description covers scope and filtering but says nothing about what a returned record contains or how paging interacts with limit, leaving the agent to discover the result shape empirically. Adequate, but not fully complete given the tool's complexity.

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 100%, so the baseline is 3, but the description genuinely enriches it: it clarifies that 'ask' means asking price and 'value' means Census owner-reported value, which disambiguates the metric and sort enums, and it explains that the level parameter drives enumeration of records at that geography. Remaining params (q, page, limit, state) are only covered by 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 names a specific verb (Search) and resource (the published 50-state and DC housing dataset) plus the usable geography axes and price dimensions. The '50-state and DC' scoping implicitly separates it from the NYC- and Florida-specific siblings, but no sibling is named explicitly, so differentiation is inferred 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 closing sentence 'Use a geography level to enumerate its records' is a usage hint, and the scope line implies when this broad dataset applies versus the metro-specific tools. However, there is no explicit when-not-to-use guidance and no routing to sibling tools for narrower geographies, so the agent must infer the boundary.

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.