Skip to main content
Glama

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

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered structurally. The description adds genuinely new context beyond that: the data provenance (HUD annual FMR dataset) and that access is free/no-cost. It omits other behavioral facts an agent would want, such as the data vintage/year and update cadence, so it is additive but not rich.

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 short sentences, front-loaded with what the tool returns, followed by use cases and provenance. There is no filler, though the fragment 'Free.' is terse enough to read as a tag rather than a sentence.

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 carries some burden for return values, and it does state the result is FMR by metro and bedroom count, which is adequate. The main remaining gap is the data year/vintage and the optional-parameter default, minor for a simple two-parameter lookup.

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 only 50%: metro_area is documented in-schema with format examples, but bedroom_count has no description and only a 0-4 range. The description does not compensate — it never explains that 0 likely means studio, nor what happens when the optional bedroom_count is omitted. Meaning added beyond the schema is minimal.

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 first sentence names the specific dataset, the resource (Fair Market Rents), and the two dimensions of the lookup (metro area, bedroom count), which is enough to distinguish it from generic siblings like get_rental_market_benchmark. It does not explicitly contrast with any sibling, so it stops short of a 5.

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 description lists four concrete downstream applications (Section 8 HCV compliance, LIHTC income limits, affordable housing underwriting, housing authority budgeting), which implies the right usage context. However, it gives no when-not conditions, no guidance on when to prefer a sibling such as get_rental_market_benchmark, and no prerequisites, so selection guidance remains inferred.

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