Skip to main content
Glama

Glazed Data Rent Limits

All rent ceilings for one unit

rent_ceilings_for_unit
Read-only

Every rent ceiling for one unit in one answer: HUD Fair Market Rent, which is free and needs no key; the tax-credit (LIHTC) rent limit, on PRO and up; and the local housing agency's voucher payment standard, on ULTRA and up. Each paid part counts as 1 call of your plan, so this tool uses 1 call on PRO and 2 on ULTRA or MEGA. Parts your plan doesn't include are skipped and not charged. Paid parts are available on: PRO ($29/month, 5,000 calls), ULTRA ($99/month, 50,000 calls), MEGA ($299/month, 250,000 calls). The paid parts need 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>",
      "bedroom_count": "<bedroom_count>"
    },
    "name": "rent_ceilings_for_unit"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior5/5

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

Annotations cover only the safe-read profile (readOnlyHint, destructiveHint:false, openWorldHint:false), and the description adds substantial non-obvious context: per-call cost (1 call on PRO, 2 on ULTRA/MEGA), that missing plan parts are silently skipped and not charged, and that a personal API key must be supplied via the x-api-key header. Cost and auth requirements are exactly the behaviors an agent cannot get from the schema.

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?

The purpose is front-loaded in the first clause, which is good, but the bulk of the text is a pricing/plan enumeration ($29/5,000 calls, $99/50,000, $299/250,000) and a signup URL that crowd out substantive guidance. The cost-per-call fact could be stated once without the full tier table.

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 3-parameter read tool with no output schema, the description explains billing and auth well but leaves two gaps: what the answer looks like when a part is skipped (omitted key vs null vs error) and what bedroom_count/fips actually control. The plan-dependent shape of the response is the main unknown an agent faces here.

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 67% and the description adds no parameter meaning at all — it never mentions zip_code, bedroom_count, or the optional fips override. bedroom_count in particular has no schema description (only min/max), so the description should have explained that it drives which unit's ceilings are returned, and it does not.

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?

"Every rent ceiling for one unit in one answer" states a specific resource and scope, and names the three concrete data sources it aggregates (HUD Fair Market Rent, LIHTC rent limit, voucher payment standard). That implicitly contrasts with the per-source siblings, though it never says "use this instead of fair_market_rent + tax_credit_limits + local_payment_standard."

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?

The description gives plan-gating rules (which parts exist on PRO/ULTRA/MEGA) and skip behavior, which helps an agent decide whether the answer will be complete. However, it never tells the agent when to pick this aggregator versus a single-source sibling tool, so the core use/use-not decision 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