Skip to main content
Glama

Contract Clock: HUD Section 8 contract expirations

Section 8 property and its contracts

get_property
Read-onlyIdempotent

One HUD Section 8 or assistance property with every contract on it: address, county, total units, HUD property category and financing type, FHA number, and per contract the number, program, status, effective date, both expiration dates, term, assisted units and rent-to-FMR ratio. Look up by contract number, HUD property ID, or property name within a state.

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_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city, to narrow a name search.
nameNoProperty name or part of it, e.g. "Carvel Gardens" (needs "state").
stateNoTwo-letter state code. Optional with a contract number.
property_idNoHUD property ID, e.g. 800003809 (needs "state").
contract_numberNoHUD contract number, 11 characters, e.g. DE26M000010.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The read-only annotations already establish the safety profile, and the description adds substantial value by specifying that the tool returns one property with every contract and by enumerating the returned fields. It does not cover no-match behavior or whether name searches can ever return multiple properties.

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?

The description is front-loaded with the resource and returned data, then closes with lookup methods. It contains no filler, and the field enumeration is justified because there is no output schema.

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 does the necessary work of explaining the returned property and contract fields. One gap remains: the schema marks zero required parameters, while the tool logically needs at least one lookup key, and the description does not explicitly state that constraint.

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 five parameters, including examples and state requirements. The description restates the lookup modes in combined form but adds little semantic detail beyond what the schema provides.

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 clearly identifies a single HUD Section 8 property and enumerates the contract-level data returned, making it distinct from aggregate or filtered-list siblings. It does not explicitly name or contrast those siblings, which keeps it from a 5.

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?

It implies usage by listing three lookup keys: contract number, HUD property ID, or property name within a state. However, it gives no explicit when-to-use guidance relative to sibling tools and does not state exclusions or prerequisites beyond the lookup keys.

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