Skip to main content
Glama

get_housing_supply_benchmark

Read-only

Live housing supply indicators — starts, permits, completions, and absorption by market tier from FRED and Census. Leading indicator for housing prices 6-12 months ahead. For developers, lenders, investors, and housing policy 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_housing_supply_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo
structure_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description adds genuinely useful material beyond them: data provenance (FRED and Census), the fact that figures are live, and an explicit $0.02 USDC cost per call. It does not disclose update frequency, the observation window, or whether values are seasonally adjusted — relevant caveats for a live economic series.

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?

Four clipped sentences, front-loaded with the core verb-and-resource statement, then the analytical use, the audience, and the price. Nothing is repeated and every sentence adds a distinct piece of information.

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 the description should orient the agent to what comes back, and listing the four indicator types plus their granularity ('by market tier') does most of that work. Given only two optional enum parameters and annotations that already cover the safety profile, the definition is close to sufficient; stated defaults and update cadence are the main things missing.

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 description coverage is 0%, so the description carries the burden, and it only partly compensates: 'by market tier' gestures at structure_type and the metric list hints at what changes with region, but neither parameter is explained. Because both parameters are enums whose valid values are self-documenting, and both are optional, the gap is smaller than a raw 0% coverage would suggest — but the absence of stated defaults (what happens when region or structure_type is omitted) is a real omission.

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 resource (housing supply indicators) and enumerates the measures it covers — starts, permits, completions, absorption — plus the upstream sources (FRED and Census). It is clearly distinguishable from the benchmark-family siblings on subject matter alone, though it never explicitly contrasts itself with a named alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete usage frame: a leading indicator for housing prices 6-12 months ahead, aimed at developers, lenders, investors and policy analysts. That is clear when-to-use context, but there are no exclusions or conditions telling an agent when another tool (e.g. a construction cost or CRE debt benchmark) would be the better pick.

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