Skip to main content
Glama

FigureDeck US Mortgage Data

Search 2026 US conforming loan limits by county

search_conforming_limits

Look up the FHFA conforming loan limit for a US county in calendar year 2026 — the maximum loan Fannie Mae and Freddie Mac will buy, for 1- to 4-unit properties. Covers all 3235 counties and county equivalents. Returns the baseline for counties with no special designation, and flags the 160 high-cost counties whose limit is above it. Pass a county name, a 5-digit FIPS code, or a state to list its counties.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_conforming_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsNo5-digit county FIPS, e.g. '53033'. Takes precedence over county.
limitNoMax rows to return, 1-100. Default 10.
stateNoTwo-letter state code, e.g. 'WA'. Filters results; on its own, lists that state's counties.
countyNoCounty name, with or without 'County'/'Parish' and state, e.g. 'King County, WA' or 'king'.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
sourceYes
matchedYesHow many counties matched the query, before truncation.
citationYes
countiesYes
returnedYes
truncatedYes
baseline_limitYesThe 1-unit limit that applies in counties with no special designation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses coverage (all 3235 counties), the baseline-vs-high-cost distinction for 160 counties, and the identifier forms accepted, but does not say what happens on no match, whether the data is read-only (implied by 'look up'), rate limits, or error behavior.

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?

Three tight sentences front-loaded with the core purpose, then coverage, then invocation. No filler; slightly packed but every sentence contributes useful facts.

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?

An output schema exists, so return values need not be explained, and the description still adds useful context about baseline vs high-cost counties. It is complete enough for a read-only reference lookup with fully documented parameters, though it omits error/no-match behavior.

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%, so the schema already documents all four parameters, including precedence and the 1-100 limit bound. The description adds only a summary of the accepted identifier forms, which is marginal beyond the schema and does not explain precedence or default-limit behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Look up the FHFA conforming loan limit'), plus scope: calendar year 2026, US counties, 1- to 4-unit properties, and the exact program (Fannie Mae/Freddie Mac). An agent can tell this is a reference-data lookup distinct from the sibling affordability and mortgage_payment tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation guidance: pass a county name, a 5-digit FIPS code, or a state, and notes that a state on its own lists that state's counties. It does not explicitly exclude alternatives or say when to prefer this over the sibling affordability/mortgage_payment tools, but the domain is clearly separate.

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