Skip to main content
Glama

BRAINIAC Official Property & Energy Lookups

Look up HUD Fair Market Rents (FY2027)

property-official_hud-fmr-lookup
Read-onlyIdempotent

Return HUD FY2027 Fair Market Rents for a county/town FIPS or HUD area, or Small Area FMRs for a ZIP, from vendored HUD files before you buy, let, or market a property. Call with optional fips, hudAreaCode, zip, bedrooms, year. Returns year, effectiveFrom, effectiveTo, zip, and safmr (safmr includes hudAreaCode, hudAreaName, rent, paymentStandard90, paymentStandard110). HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you buy, let, or market a property, fips, hudAreaCode, zip, bedrooms, year, effectiveFrom, effectiveTo, safmr, Look up HUD Fair Market Rents (FY2027), hud fmr lookup.

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": "property-official_hud-fmr-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNozip, string. Optional.
fipsNofips, string. Optional.
yearNoyear, number. Required.
bedroomsNobedrooms, value. Optional.
hudAreaCodeNohudAreaCode, string, length 3 to 40. Optional.

Output Schema

NameRequiredDescriptionDefault
zipNozip. String.
yearNoyear. Number.
safmrNosafmr. Array.
sourcesNosources. Array.
effectiveToNoeffectiveTo. String.
limitationsNolimitations. Array.
effectiveFromNoeffectiveFrom. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: results come from vendored HUD files, and HTTP 200 responses with status complete, partial, or failed are billed at full price while 4xx/5xx are free — a cost consideration the agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence and the billing/return sentences are front-loaded and earn their place, but the trailing 'Keywords:' block restates the title, the usage phrase, and every parameter name verbatim — pure repetition that adds length without 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?

An output schema exists, so the description need not explain return values in depth, yet it summarizes the key fields (year, effectiveFrom/To, safmr with paymentStandard90/110). Combined with the billing rules and data source, this is nearly complete; only the interaction rules among the three geographic selectors are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by presenting fips, hudAreaCode and zip as alternative ways to address the query, which the schema does not convey since every property is marked optional with no required list. It stops short of stating whether these selectors are mutually exclusive or which takes precedence.

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?

States a specific verb and resource ('Return HUD FY2027 Fair Market Rents') and immediately distinguishes the two modes: county/town FIPS or HUD area for FMRs versus ZIP for Small Area FMRs. An agent knows exactly what data comes back 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 Guidelines4/5

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

Gives a concrete usage context ('before you buy, let, or market a property') and ties the selector choice to the caller's identifier type. It does not name alternatives, but the sibling tools cover entirely different domains (radon, price cap, UK HPI), so there is little real ambiguity to resolve.

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