Hud

Hud Income Limits

hud_income_limits

Read-onlyIdempotent

Check income eligibility thresholds (extremely low, very low, low-income) for HUD programs by area and family size. Returns income limits by category. Use to determine program qualification.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Fiscal year (e.g., 2024). Omit for the most recent year.
`_apiKey`	Yes	HUD API token
`entity_id`	No	FIPS code or metro area code for a specific area. Omit to get all areas in the state.
`state_code`	Yes	Two-letter state code (e.g., "CA", "NY").

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Income limits data from HUD API
`year`	Yes	Fiscal year requested or 'latest'
`state`	Yes	Two-letter state code provided in request
`entity_id`	Yes	FIPS code or metro area code if provided, null otherwise

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-hud-api-key",
-    "state_code": "TX"
-  },
-  {
-    "_apiKey": "your-hud-api-key",
-    "entity_id": "06037",
-    "state_code": "CA",
-    "year": 2024
-  }
-]New value: +[
+  {
+    "state_code": "TX"
+  },
+  {
+    "entity_id": "06037",
+    "state_code": "CA",
+    "year": 2024
+  }
+]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Income limits data from HUD API",
+      "type": "object"
+    },
+    "entity_id": {
+      "description": "FIPS code or metro area code if provided, null otherwise",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "description": "Two-letter state code provided in request",
+      "type": "string"
+    },
+    "year": {
+      "description": "Fiscal year requested or 'latest'",
+      "type": [
+        "number",
+        "string"
+      ]
+    }
+  },
+  "required": [
+    "state",
+    "entity_id",
+    "year",
+    "data"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-hud-api-key",
+    "state_code": "TX"
+  },
+  {
+    "_apiKey": "your-hud-api-key",
+    "entity_id": "06037",
+    "state_code": "CA",
+    "year": 2024
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds modest context by saying the tool returns income limits by category, but it does not disclose behaviors like defaulting to all areas when entity_id is omitted or any pagination/rate-limit details.

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?

Two sentences, no filler, with the key purpose and the return categories front-loaded. The final sentence gives a concrete usage prompt.

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?

For a simple lookup tool with full schema coverage, annotations, and an output schema, the description is nearly complete for safe invocation. The only gap is that 'by family size' has no corresponding parameter and no explicit distinction from the HUD fair market rents sibling.

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 fully documents year, entity_id, state_code, and _apiKey. The description adds output-category context but does not clarify parameter meaning beyond the schema; it even says 'by family size' without a family_size parameter, which could create mild ambiguity.

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 verb ('Check') and resource ('income eligibility thresholds... for HUD programs'), and names the three income categories returned. It is clearly about income limits rather than fair market rents, but it does not explicitly distinguish itself from a sibling like hud_fair_market_rents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use to determine program qualification' gives a clear intended use case and implied context for the tool. However, it does not state when not to use it or point to alternatives such as hud_fair_market_rents or hud_chas.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hud tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.