Skip to main content
Glama

FDIC-insured banks by commercial real estate concentration

search_bank_cre_exposure
Read-onlyIdempotent

Search 4,313 FDIC-insured banks by their commercial real estate book at the June 2026 call report: total CRE, construction and multifamily in dollars and against equity and assets, noncurrent and net charge-off ratios, ROA, and two screens against the 2006 Interagency CRE guidance (construction over 100%, total CRE over 300%). For 4,242 of them, UBPR's peer-group and national percentile RANKS on the same concentrations. Filter by state, name, CRE-to-equity range, guidance screen, minimum assets or minimum noncurrent ratio; sort by cre_to_equity (default), construction_to_equity, noncurrent, cre_total, assets or multifamily. Free. THE GUIDANCE IS QUOTED, NOT APPLIED: it tests TOTAL RISK BASED CAPITAL; the ratios here are on equity and the ranks on Tier 1 plus the allowance, so above_*_guidance_on_equity is a screen against a proxy. Every row states its quarter. No person appears in this data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSubstring of the institution name, case-insensitive, e.g. 'riverhills'.
sortNoDescending on the named measure. Default cre_to_equity.
limitNoRows to return, 1 to 50. `matched` states the true total regardless.
stateNoTwo-letter US state, district or territory code of the bank's home office. Unknown codes are refused, not searched.
above_guidanceNotrue: only banks whose total CRE exceeds 300% of equity (the guidance line, on a proxy denominator). false: only banks under it.
min_assets_usdNoFloor on total assets in dollars, e.g. 1000000000 for $1B.
min_noncurrent_pctNoFloor on the CRE noncurrent ratio in percent.
max_cre_to_equity_pctNoCeiling on the same ratio.
min_cre_to_equity_pctNoFloor on total CRE as a percent of equity, e.g. 300.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description still adds substantial behavioral context beyond them: the guidance is 'QUOTED, NOT APPLIED' and uses an equity-based proxy rather than total risk-based capital, every row states its quarter, and 'no person appears in this data'. This discloses data provenance and proxy limitations the agent would otherwise misread.

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?

Dense but front-loaded: purpose and dataset scope lead, then a separate paragraph for the critical proxy caveat. The first paragraph is a long run-on, but nearly every clause carries distinct information and the caveat paragraph earns its place given the ambiguity it resolves.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 optional parameters and no output schema, the description carries the full burden and meets it: it describes the returned fields, the 4,313 vs 4,242 coverage split, percentile rank availability, the proxy caveat, and that 'matched' reports the true total. An agent has everything needed to call and interpret it correctly.

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 9 parameters. The description's filter list (state, name, CRE-to-equity, guidance screen, minimum assets/noncurrent) and its mention of the default sort largely restate what the schema provides, adding little beyond it. Baseline 3 is correct.

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 (Search) and resource (4,313 FDIC-insured banks by commercial real estate book) with the exact data vintage (June 2026 call report). It enumerates the measures returned (total CRE, construction, multifamily, noncurrent, charge-off, ROA, guidance screens) so an agent knows precisely what this resource covers and how it differs from the finance-domain siblings.

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 implies usage by listing the available filters (state, name, CRE-to-equity range, guidance screen, minimum assets, minimum noncurrent) and sorting options, and flags that it is 'Free'. However, it never states when to prefer this over an alternative or any prerequisite/context for choosing it, so guidance is implied rather than explicit.

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.