Skip to main content
Glama

Glazed Data Rent Limits

Local housing agency payment standard

local_payment_standard
Read-only

The local housing agency's own voucher payment standard for a ZIP, with its effective date and source document. 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": "local_payment_standard"
  }
}

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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 does add genuinely useful non-annotation context: an x-api-key header requirement, a key-creation URL, and the paid plan tiers that gate access. It does not disclose rate limits, error behavior, or response shape, so the addition is meaningful but modest.

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 purpose is front-loaded in the first sentence and the second sentence is compact. The pricing/plan detail ($99/$299, call counts) is somewhat promotional and bulks up a short description, but it is relevant to whether the caller can use the tool at all.

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 3-parameter read-only lookup with full schema coverage and no output schema, the definition covers what the tool returns (standard value, effective date, source document), the auth mechanism, and access constraints. Gaps are minor: no mention of behavior when a ZIP spans multiple HUD areas, which is precisely what the fips parameter exists for.

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% and each parameter (zip_code, fips, bedroom_count) is documented in the schema itself. The description adds only the notion of ZIP scoping and does not explain the fips fallback or the 'all' bedroom default beyond what the schema already says. Baseline 3 applies.

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 with a clear qualifier: 'the local housing agency's own voucher payment standard for a ZIP,' plus the returned fields (effective date, source document). It implicitly separates itself from the fair_market_rent and rent_ceilings_for_unit siblings by emphasizing the agency's *own* standard, though it never names those alternatives.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The plan/auth sentences describe access conditions rather than the decision criteria for picking this tool over fair_market_rent or rent_ceilings_for_unit.

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