Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

Conforming and FHA loan limits for a ZIP code

get_loan_limits
Read-onlyIdempotent

The conforming and FHA loan limits for the counties a five-digit ZIP code falls in, for the 2026 published schedule, as freerateupdate.com publishes them at https://www.freerateupdate.com/loan-limits. Each limit carries the official source it came from (FHFA for conforming, HUD for FHA) and, when a check has run, the date that source was last confirmed. These are published limits, not advice: a limit is not a rate, an approval or an offer, and eligibility depends on the lender and the loan.

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": "<zip>"
    },
    "name": "get_loan_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesFive-digit ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the upstream publisher, the official per-limit sources (FHFA for conforming, HUD for FHA), and the conditional 'when a check has run' confirmation date, which tells the agent a field may sometimes be absent.

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 resource and scope are front-loaded in the first clause, and the following sentences cover provenance and the advice disclaimer. The URL and the slightly repetitive 'not advice / not a rate / not an approval' construction add some bulk, but each part carries informational weight.

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 takes on the burden of describing returns and does so: it explains that each limit carries its official source and a last-confirmed date. It is complete enough for a one-parameter read tool, with only multi-county ZIP behavior left unaddressed.

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 coverage is 100% and the single parameter is already documented as a five-digit ZIP with a pattern. The description restates the same constraint without adding format, normalization or edge-case behavior (for example ZIPs spanning multiple counties), so 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?

The description names a specific resource pair (conforming and FHA loan limits) scoped to the counties of a five-digit ZIP for the 2026 schedule, which is far more precise than the title alone. It does not name any sibling tool explicitly, but the line 'a limit is not a rate' implicitly separates it from get_mortgage_rates and get_heloc_rates.

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?

Usage is implied rather than stated: an agent can infer this is the tool for geographic limit lookups and not for rate quotes, thanks to the disclaimer sentence. There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as the alternative for adjacent questions.

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