Skip to main content
Glama

Endorsement Index: HUD multifamily loans

HUD application exhibit checklist

hud_checklist
Read-onlyIdempotent

The exhibits HUD lists for an application, in HUD's order, with tab, file name, requirement, citation and form links: 223(f) firm, 223(a)(7) firm, 221(d)(4) pre-application and firm, Transfer of Physical Assets, and Section 8 renewal. Omit program for the list of checklists.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
programNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety behavior is covered. The description adds value beyond that by disclosing the return payload shape (tab, file name, requirement, citation, form links) and the ordering guarantee ('in HUD's order'). It says nothing about pagination behavior despite limit/offset being present.

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 what is returned, then the program enumeration, then the omit rule. Nearly every clause carries information, though the program list is dense and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema, the description covers purpose, return fields and program selection well. The gap is pagination: with limit capped at 50 and an offset, an agent needs to know whether results are paged and how to iterate, and nothing here or in the schema says so.

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 0%, so the description must carry the burden. It does well for `program`: all six enum slugs are spelled out in human-readable form and the omit-for-all behavior is explained. However, limit and offset are never mentioned, so the pagination parameters remain undocumented in both schema and description.

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 a concrete resource (the exhibits HUD lists for an application) and states what it returns: tab, file name, requirement, citation and form links, in HUD's order. It also enumerates the supported programs, which makes the scope unambiguous. It does not explicitly contrast with siblings, but the resource is distinct enough that an agent can route to it without opening another schema.

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 sentence 'Omit program for the list of checklists' gives real usage guidance for the optional-parameter case and implies that supplying a program selects one checklist. Beyond that there is no when-to-use framing and no mention of alternatives among siblings such as program_facts or hud_stats.

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