Skip to main content
Glama

Stratalize Intelligence

Get Housing Supply Benchmark

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the external data provenance (FRED, Census) and a per-call price of $0.02 USDC, which matters for an agent deciding whether to invoke it. It stops short of disclosing data freshness, latency, or caching behavior.

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 tight sentences, front-loaded with the data content before the use case and price. The audience list is the weakest element and borders on filler, but it is short enough not to dilute the definition.

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 two-optional-parameter benchmark tool with no output schema, the description covers what data is returned at a high level and its cost, but omits the default scope when no region/structure_type is supplied and says nothing about the shape or granularity of the response. Adequate but with clear gaps for correct invocation.

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 carries the full burden, yet it never explains what 'region' or 'structure_type' control. The phrase 'by market tier' is ambiguous and does not map cleanly onto either parameter, and with both parameters optional there is no statement of what defaults apply when they are omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (housing supply indicators: starts, permits, completions, absorption) and its upstream sources (FRED and Census), which cleanly separates it from adjacent siblings like get_construction_cost_benchmark or get_development_pro_forma_benchmark. An agent can identify the tool's domain without opening the schema.

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?

It gives a use-case framing ('leading indicator for housing prices 6-12 months ahead') and an audience list (developers, lenders, investors, policy analysts), which implies when the tool is relevant. However, it never states when NOT to use it or names an alternative tool for related questions, so routing guidance is only implied.

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