Skip to main content
Glama

Glazed Data Rent Limits

Tax-credit (LIHTC) rent and income limits

tax_credit_limits
Read-only

Tax-credit (LIHTC/MTSP) rent and income limits for a US ZIP code, all income tiers, with held-harmless limits by placed-in-service date. 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": "tax_credit_limits"
  }
}

Input Schema

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

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?

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description meaningfully adds what annotations cannot: the x-api-key auth requirement and monthly call caps per plan tier (5,000 / 50,000 / 250,000). It does not describe response shape or per-request rate limiting, so it falls short of fully rich behavioral context.

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 functional scope is front-loaded in the first sentence and the auth/plan constraints follow. The enumeration of three plan price points is somewhat bulky for the value it adds, but it is not padding — it tells the agent whether the caller is even entitled to invoke the tool.

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 carries the burden of telling the agent what comes back; it covers tiers and held-harmless limits but not the response structure. All four parameters are documented in-schema, and the account/auth constraints are stated, so an agent has enough to call this correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description earns one step above that by explaining that held-harmless limits vary with placed-in-service date, giving semantic meaning to the placed_in_service parameter, and by stating 'all income tiers' as the default scope.

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 names a precise resource and scope: tax-credit (LIHTC/MTSP) rent and income limits for a US ZIP code, covering all income tiers and held-harmless limits by placed-in-service date. The program name (LIHTC/MTSP) implicitly separates it from the Section 8 and fair-market-rent siblings, but it never explicitly contrasts itself with them.

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 gives prerequisites (an API key in x-api-key and a PRO/ULTRA/MEGA subscription) but no explicit when-to-use guidance relative to siblings like section8_income_limits or fair_market_rent. An agent can infer the context from the LIHTC framing, but the choice among the limit-type tools is left to inference.

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