Skip to main content
Glama

Contract Clock: HUD Section 8 contract expirations

Section 8 HAP contracts paying under Fair Market Rent

screen_below_fmr
Read-onlyIdempotent

The deal screen's rent test for one state: active Section 8 HAP contracts whose rent-to-FMR ratio in HUD's file is above zero and under a threshold (default 90%), with property, assisted units, ratio, both expiration dates and a prefilled offer-calculator link. Optional filters: county, city, minimum assisted units, overall expiration within N months.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "screen_below_fmr"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city name, e.g. "Cleveland".
sortNoLowest ratio first (default), largest first, or soonest overall expiration first.rent_to_fmr
limitNoRows to return, 1 to 20 (default 10); page with offset for more.
stateYesTwo-letter state or territory code, e.g. OH.
countyNoOptional county name as HUD spells it, e.g. "Cuyahoga".
offsetNoRows to skip, for paging.
max_rent_to_fmrNoKeep contracts whose rent-to-FMR ratio is under this percent (default 90, the deal screen's line).
min_assisted_unitsNoOptional minimum assisted units (the state page table uses 20).
expiring_within_monthsNoOptional: only contracts whose overall expiration falls within this many months of the HUD file date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, non-destructive, idempotent, closed-world operation. The description adds useful behavioral context beyond annotations: it specifies that only active contracts are returned, describes the ratio condition, and names the fields and prefilled offer-calculator link included in results. It does not address auth or rate limits, but those are less critical here.

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?

The description is two sentences, front-loaded with the core screening logic, then the return payload, then optional filters. It is dense but appropriately sized for a 9-parameter tool, with little wasted language.

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?

There is no output schema, so the description usefully names the return fields and prefilled calculator link. It also covers the threshold behavior and optional filters. Pagination and sorting are left to the fully documented schema, which is acceptable; the definition is complete enough for correct invocation.

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 the schema already documents all nine parameters thoroughly. The description restates the default threshold and lists optional filters, but adds no syntax, format, or edge-case semantics beyond what the schema provides. Baseline 3 is appropriate when structured fields carry the parameter burden.

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 states a specific resource and screening condition: active Section 8 HAP contracts where rent-to-FMR is above zero and below a configurable threshold. It clearly identifies the tool's scope by state and lists returned fields, though it does not explicitly distinguish itself from siblings like expiring_contracts or state_contract_summary.

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 phrase 'deal screen's rent test for one state' implies the intended context, and optional filters are listed. However, there is no explicit guidance on when to choose this tool over expiring_contracts, get_property, or state_contract_summary, nor any stated exclusions or prerequisites.

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