Skip to main content
Glama

Glazed Data Rent Limits

Voucher headroom and renter demand

voucher_headroom_and_renter_demand
Read-only

Voucher headroom against tax-credit rents and renter-household counts (HUD CHAS) for a ZIP. Available on: 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": "voucher_headroom_and_renter_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsNoOptional HUD area or county code, when a ZIP spans several areas
tierNo
zip_codeYes5-digit US ZIP code
bedroom_countNoBedroom count 0-5, or "all" (default)
placed_in_serviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds genuinely useful invocation prerequisites the annotations don't carry: the required x-api-key header, where to obtain the key, and which subscription tiers can call it. It stops short of describing response shape or units of 'headroom'.

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, front-loaded with the data the tool returns, then the access requirements. Nothing redundant, and the pricing detail, while marketing-adjacent, is short and actionable.

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?

For a read-only tool with no output schema and five parameters, the description covers purpose and access but leaves two parameters undefined and gives no hint about the shape or interpretation of the returned headroom figures. Adequate to start a call, thin for calling it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 60%, and 'tier' and 'placed_in_service' have no description anywhere. The description adds nothing beyond restating that the call is 'for a ZIP' — fips, bedroom_count, and placed_in_service semantics remain unexplained.

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?

Names a specific subject (voucher headroom vs. tax-credit rents and renter-household counts from HUD CHAS) scoped to a ZIP. An agent can tell what data comes back, though it doesn't say how this differs from siblings like tax_credit_limits or section8_income_limits.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the sibling tools that overlap (rent_ceilings_for_unit, section8_income_limits, tax_credit_limits). The only conditional content is plan availability and API key setup, which is access guidance rather than selection 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