Skip to main content
Glama

get_residential_market_benchmark

Read-only

Residential real estate market benchmarks — home price indices, price-to-rent ratios, affordability, months of supply, and homeownership rate by market tier. Sources: FHFA HPI, FRED live data, Census. For residential investors, agents, developers, and housing analysts. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
market_tierNo
property_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the description's added value is the data provenance (FHFA HPI, FRED live data, Census) and the per-call price of $0.02 USDC — genuinely useful operational context an agent cannot get from structured fields. Gaps remain: no statement of geographic granularity, update cadence, or what an empty/omitted-filter 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?

Three compact sentences with the metric scope front-loaded, then provenance, then audience and price. No redundancy or hedging; every clause carries information.

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 parameterless-optional read-only benchmark query with no output schema, the description adequately signals the metric set and cost. However, it is silent on the two optional enum parameters' effects and on default behavior when both are omitted, which is precisely the ambiguity an agent would hit when calling it.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning — it does not. 'By market tier' vaguely gestures at market_tier but never explains the tier values (national/gateway_metro/secondary_metro/tertiary), and property_type is never mentioned at all despite shaping the metrics returned.

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+resource ('Residential real estate market benchmarks') and enumerates the concrete metrics returned — HPI, price-to-rent, affordability, months of supply, homeownership rate. This distinguishes it from 'benchmark' tools generally, though it never explicitly contrasts with close siblings such as get_rental_market_benchmark or get_mortgage_market_benchmark.

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 only usage signal is an audience list ('For residential investors, agents, developers, and housing analysts'), which implies the call context but gives no when-to-use, when-not-to-use, or alternative routing. An agent must infer the boundary between this and the rental/mortgage benchmark siblings from the metric list alone.

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