Skip to main content
Glama

Glazed Data Rent Limits

HUD Fair Market Rent for a ZIP

fair_market_rent
Read-only

HUD Fair Market Rent and Small Area FMR for a US ZIP code, by bedroom count, with effective dates and source links. Free, no key needed.

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": {
      "zip_code": "<zip_code>"
    },
    "name": "fair_market_rent"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsNoOptional HUD area or county code, when a ZIP spans several areas
zip_codeYes5-digit US ZIP code
bedroom_countNoBedroom count 0-4, or "all" (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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=false, so the safety profile is covered structurally. The description adds real value by disclosing the no-key auth requirement and the shape of the return (effective dates and source links), but says nothing about rate limits, pagination, or what happens when a ZIP maps to multiple HUD areas.

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?

Two short sentences, front-loaded with the resource and scope, followed by the access note. Every clause carries information and there is no filler.

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 usefully previews the return contents (effective dates, source links) and removes auth uncertainty with 'no key needed'. For a simple three-parameter read-only lookup this is nearly complete, though it omits guidance on the fips fallback path when a ZIP spans areas.

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 100%, so all three parameters, including the ambiguous fips fallback and the bedroom_count 'all' enum, are already documented in the schema. The description's phrase 'by bedroom count' mirrors the schema rather than adding new semantics, so baseline 3 is appropriate.

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 the exact resource (HUD Fair Market Rent and Small Area FMR) and its scope (US ZIP code, by bedroom count), which is specific enough for an agent to recognize the lookup. However, it does not distinguish itself from siblings like rent_ceilings_for_unit or voucher_headroom_and_renter_demand, leaving the agent to infer the boundary.

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

Usage Guidelines2/5

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

'Free, no key needed' tells the agent about access cost but not when to choose this tool over the rent-ceiling or payment-standard siblings. No when-to-use, when-not-to-use, or alternative routing is stated.

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