Skip to main content
Glama

Glazed Data Rent Limits

HUD Section 8 income limits

section8_income_limits
Read-only

HUD Section 8 income limits (30%, 50%, 80%) by household size for a US ZIP code. Available on: PRO ($29/month, 5,000 calls), ULTRA ($99/month, 50,000 calls), MEGA ($299/month, 250,000 calls). Needs your own Glazed Data API key in the x-api-key header (create one at https://glazeddata.com/rent-limits/pricing/).

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": {
      "zip_code": "<zip_code>"
    },
    "name": "section8_income_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsNoOptional HUD area or county code, when a ZIP spans several areas
zip_codeYes5-digit US ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational context beyond that: it requires the caller's own Glazed Data API key in the x-api-key header and states per-plan call quotas (5,000 / 50,000 / 250,000). It does not say what the response looks like or how ZIPs spanning multiple areas are resolved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, which is good structure. The second and third sentences are dominated by pricing tiers and key-setup instructions, which are useful for quota awareness but crowd out data-shape details for a two-parameter tool.

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?

Auth, quota, and the data's scope are covered, and there is no output schema to explain. However, the definition never clarifies the returned structure (income limits per household size) or how fips overrides ZIP-level lookup, which matters for a tool whose whole value is a multi-column limits table.

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 both zip_code and fips are already documented, and the description adds no syntax or format detail. It does mention household size, which appears nowhere in the input schema, leaving mild ambiguity about whether household size is an input or a dimension of the returned table.

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 and scope: HUD Section 8 income limits at 30/50/80% by household size for a US ZIP code. An agent can tell what data it returns, but nothing distinguishes it from siblings like fair_market_rent, tax_credit_limits, or rent_ceilings_for_unit.

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

Usage Guidelines2/5

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

No guidance on when to choose this over the other rent/limit tools in the family, nor any prerequisites beyond the API key. The only conditional information is plan-tier availability, which is commercial rather than usage guidance.

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