Skip to main content
Glama

Stratalize Healthcare

Get Hud Fair Market Rent

get_hud_fair_market_rent
Read-only

HUD Fair Market Rents by metro area and bedroom count. Used for affordable housing underwriting, Section 8 Housing Choice Voucher compliance, LIHTC income limit calculations, and housing authority budgeting. Source: HUD annual FMR dataset. Free.

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": {
      "metro_area": "<metro_area>"
    },
    "name": "get_hud_fair_market_rent"
  }
}

Input Schema

NameRequiredDescriptionDefault
metro_areaYese.g. Chicago, IL or Miami, FL
bedroom_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, open-world behavior, so the description's marginal contribution is provenance and cost: HUD as the source, an annual dataset (implying data lag), and 'Free' (no auth or billing friction). Those are genuinely useful additions, but it says nothing about return shape, units, or whether bedroom_count defaults when omitted.

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?

Four short sentences, front-loaded with the resource and its dimensions, then use cases, then provenance. Every sentence carries information, though 'Free.' and the source line are terse fragments rather than fully formed statements.

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?

For a simple two-parameter lookup with no output schema, the definition covers what the data is, where it comes from, and what it is used for. The remaining gaps are output field expectations and bedroom_count defaulting, which are minor for a single-row benchmark lookup.

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 50%: metro_area carries an example format ('Chicago, IL'), while bedroom_count has only min/max bounds and no explanation. The description confirms both are query dimensions but does not clarify that bedroom_count 0 means studio or what happens if it is omitted, so it adds little beyond 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 resource (HUD Fair Market Rents) and its two dimensions (metro area, bedroom count), so an agent knows exactly what data comes back. It does not explicitly distinguish itself from plausibly overlapping siblings like get_rental_market_benchmark, which keeps it out of 5 territory.

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?

Four concrete use cases (affordable housing underwriting, Section 8 HCV compliance, LIHTC income limits, housing authority budgeting) imply when the tool applies. However, there is no when-not guidance and no routing to an alternative such as a general rental benchmark, leaving the agent to infer boundaries.

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