Skip to main content
Glama

Realtors Dashboard

Get an exact U.S. housing market

get_housing_market
Read-onlyIdempotent

Get national or exact state, county, or ZIP pricing, housing stock, and available FHFA trend data. No broader substitute is returned.

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": {
      "level": "<level>",
      "id": "<id>"
    },
    "name": "get_housing_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUS for national, USPS abbreviation for state, five-digit FIPS for county, or five-digit ZIP
levelYesGeography type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 two useful facts beyond that: the data source is FHFA and trend data is only 'available' (i.e., may be missing), plus the no-fallback behavior. It says nothing about error handling for an invalid id or what an empty result looks like.

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?

Two short sentences, front-loaded with the capability and followed by the key constraint. No filler or redundant restatement of the title.

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 only two fully documented parameters, complete annotations, and no output schema, the description covers what is returned (pricing, stock, trends) and the no-fallback rule. Only error/empty-result behavior is left unstated.

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 coverage is 100% and the id field already documents the US/USPS/FIPS/ZIP formats, so the schema carries the parameter burden. The description's geography list mirrors the level enum without adding format or validation detail beyond it.

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?

States a specific verb ('Get') and resource ('housing market') with explicit scope: national, state, county, or ZIP, covering pricing, housing stock, and FHFA trend data. The scope implicitly separates it from the NYC/Florida-specific siblings, though it never names them.

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?

'No broader substitute is returned' hints that this is the tool for exact-geography lookups rather than aggregates, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for broader or metro-level queries.

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.