Skip to main content
Glama

Endorsement Index: HUD multifamily loans

Treasury, MIP and realized HUD note rates

rates_today
Read-onlyIdempotent

The latest 10-year Treasury par yield, the current FHA multifamily MIP, and note rates on the most recently endorsed FHA-insured apartment loans by program, with sample sizes and dates, plus the 15 newest loans. Realized rates only, excluding MIP: no quote and no spread added to the Treasury.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the figures are realized rates only, MIP is excluded from them, and no quote or spread is layered on the Treasury. It also discloses that each rate is accompanied by sample sizes and dates, which signals statistical reliability. It does not explain units or output shape.

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?

Two sentences, front-loaded with the substantive data inventory, no filler. The closing clause 'no quote and no spread added to the Treasury' is terse to the point of being cryptic, but it carries real disambiguating value about what the numbers are not.

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 and no parameters, the description carries the burden of telling the agent what comes back, and it largely does: named series, per-program rates, sample sizes, dates, and the 15 newest loans. What is left unstated is the shape of the response and the units/percent basis of the rates, a minor gap for a zero-input snapshot tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to supply. Nothing is missing or contradicted on this dimension.

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 specific data series returned: the 10-year Treasury par yield, the current FHA multifamily MIP, and realized note rates on recently endorsed FHA apartment loans by program, plus the 15 newest loans. That is far more specific than the title alone. It stops short of naming a sibling tool it should be preferred over (e.g. hud_stats or program_facts), so differentiation is left to inference.

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?

Usage is only implied: an agent can infer this is the tool for current rate benchmarks rather than loan-level lookup. There is no explicit 'use this when…' or 'use X instead when…' statement, and no mention of prerequisites or freshness guarantees beyond 'latest'. The exclusion of quoted rates is a scope note, not routing guidance.

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