Skip to main content
Glama

Endorsement Index: HUD multifamily loans

Search FHA-insured apartment loans

search_loans
Read-onlyIdempotent

Search every FHA-insured apartment loan in HUD's active multifamily file by state, city, program, note rate, years left, servicer or text. Returns HUD's figures (note rate, original amount, amortized balance, maturity, holder, servicer, Section of the Act) with a property page URL. Use it to find assumable low-rate loans, loans by a servicer, or a property's FHA number.

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": "search_loans"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to match in property name, city, address, ZIP or FHA number.
cityNoCity, exact match (case-insensitive).
sortNo-amortized_balance
lihtcNo
limitNo
stateNoTwo-letter state code, e.g. TX.
offsetNo
programNo
max_rateNoMaximum note rate, percent (e.g. 4 for assumable low-rate loans).
min_rateNoMinimum note rate, percent.
servicerNoServicer name fragment, e.g. Greystone.
min_unitsNo
max_balanceNo
min_balanceNoMinimum amortized balance, US dollars.
max_years_leftNo
min_years_leftNoMinimum years to maturity.

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, non-destructive, closed-world, so the safety profile is covered; the description adds the valuable part by listing what comes back (note rate, original amount, amortized balance, maturity, holder, servicer, Section of the Act) plus a property page URL. It does not mention pagination/limit behavior or result-set size, which would complete the picture.

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?

Three sentences, front-loaded with scope, then return payload, then use cases. Every clause carries information an agent needs 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?

For a 16-parameter tool with no output schema, the description does the heavy lifting by enumerating returned fields and the property URL. It still leaves pagination semantics, sort behavior, the lihtc flag, and the units/balance filters unexplained, which is a real but modest gap.

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 only 50%, and the description's filter list (state, city, program, note rate, years left, servicer, text) largely restates parameters the schema already names. It adds nothing for the undocumented ones — lihtc, sort, limit, offset, min_units/max_units, max_balance — so it only partially compensates for the coverage gap.

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 ('Search every FHA-insured apartment loan in HUD's active multifamily file') and enumerates the filter dimensions, which implicitly separates it from the single-record sibling get_loan. The scope word 'every' plus the data source makes the tool's remit unambiguous.

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?

Explicitly names three concrete use cases — finding assumable low-rate loans, loans by a servicer, or a property's FHA number — which tells the agent when this tool is the right pick. It stops short of exclusions or naming alternatives (e.g., 'for a single known FHA number, get_loan is cheaper').

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