Skip to main content
Glama

Route 232: HUD Section 232 programs, queue and timing

HUD Section 232 queue this week

get_queue_times
Read-onlyIdempotent

HUD ORCF's weekly Section 232 underwriting queue report, summarized: how many 223(f), 223(a)(7) and new construction/241(a) applications are waiting, Express Lane counts, median and oldest days waiting, how long this week's underwriter assignments waited, the fiscal-year median wait, and optionally every saved weekly snapshot.

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

Input Schema

NameRequiredDescriptionDefault
limitNoWeeks of history to return (default 10, max 50).
offsetNoWeeks of history to skip, for paging.
include_historyNoAlso return the saved weekly snapshots, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 useful context beyond that: it is a 'summarized' weekly report rather than raw records, and the history option returns 'every saved weekly snapshot' (signaling a potentially large payload). It says nothing about data freshness timing, rate limits, or snapshot 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?

A single front-loaded sentence that opens with the resource and then lists contents; every clause adds information and nothing repeated. It is dense and slightly run-on, but no sentence is wasted.

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 carries the return-value burden and does so by naming each reported metric and the optional snapshot history. Remaining gaps are minor (when in the week the report refreshes, what a snapshot contains), and all three parameters are documented in the schema.

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 limit/offset/include_history are fully documented in the schema and the baseline is 3. The description only echoes include_history ('optionally every saved weekly snapshot') without adding format, ordering, or cost details the schema lacks.

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?

States a specific resource (HUD ORCF weekly Section 232 underwriting queue report) and enumerates the exact metrics returned (223(f), 223(a)(7), 241(a) counts, Express Lane, median/oldest wait, fiscal-year median). It is far more specific than the name alone, but never names or distinguishes itself from siblings like estimate_232_timeline, which plausibly covers similar ground.

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 enumeration of contents implies when to use it (want current queue status) but there is no explicit 'use this when...' clause, no exclusions, and no routing to alternatives such as estimate_232_timeline for projections. Usage must be inferred from the payload description.

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