Skip to main content
Glama
cliwant

mcp-sam-gov

fdic_bank_failures

Read-only

Retrieve historical FDIC-insured bank failures and assistance transactions. Filter by state, failure year, or certificate number, and sort by date, cost, or assets.

Instructions

Historical FDIC-insured bank failures & assistance transactions (keyless; api.fdic.gov/banks/failures). CERT links a failure back to fdic_search_institutions / fdic_institution_financials. Filters: state (2-letter → PSTALP — NOTE: /failures state field is PSTALP, NOT STALP), failYear (→FAILYR), cert (→CERT, the STABLE entity key). limit (≤1000), offset (≤100000), sortBy (FAILDATE/COST/QBFASSET/QBFDEP/NAME/FAILYR, def FAILDATE), sortOrder (def DESC). Returns { failures:[{ name, cert, failDate, failYear, city, state, resolutionType, resolutionFund, estimatedLossUSD, depositsUSD, assetsUSD, id }] }. NO name/city filter — FDIC /failures search param is IGNORED (returns the whole dataset); to find a specific bank's failure, resolve its CERT via fdic_search_institutions. HONESTY: totalAvailable is EXACT meta.total (stable across offset). failDate normalized from FDIC's M/D/YYYY to ISO YYYY-MM-DD (unrecognized → surfaced raw + disclosed, never nulled). COST/QBFDEP/QBFASSET are $thousands normalized to whole USD ×1000 (null-never-0 — genuine 0 = a no-loss assisted transaction stays 0; NEGATIVE COST = a net DIF recovery/gain, not a loss; absent → null). ONLY honest empty is meta.total:0/data:[] → complete:true/total:0; any other envelope (400 errors[]/404/non-JSON/missing meta or data) THROWS (never fake-empty). The point-in-time snapshot build time is disclosed. NOTE: FDIC keys on CERT, not SAM UEI/DUNS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certNoFilter by FDIC certificate number (the STABLE entity key; → CERT filter). Resolve a bank's CERT via fdic_search_institutions.
limitNoRows per page, 1..1000, default 100.
stateNoFilter by 2-letter US state code (uppercase; → PSTALP filter — the /failures state field is PSTALP, NOT STALP). e.g. 'CA'.
offsetNo0-based row offset for pagination, 0..100000, default 0.
sortByNoSort field (allowlisted enum; default FAILDATE = failure date). An unknown field is rejected before fetch.
failYearNoFilter by year of failure (→ FAILYR filter). 1934..current UTC year. e.g. 2023 → the 5 real 2023 failures (Silicon Valley Bank, Signature Bank, First Republic Bank, Heartland Tri-State Bank, Citizens Bank).
sortOrderNoSort direction, default DESC (most-recent failures first).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A5/5.0
Behavior5/5

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

Even though annotations declare readOnlyHint=true and openWorldHint=true, the description goes far beyond this: it discloses exact error behavior (honest empty vs throwing), date normalization, cost-unit conversion from thousands to whole USD, null handling, negative-COST semantics, and the fact that totalAvailable is exact. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but exceptionally dense and front-loaded with the resource and key relationships before filters, return shape, and edge cases. Every sentence carries operational information an agent needs: field mappings, sorting defaults, normalization rules, and failure behavior. There is no filler.

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?

Despite having no output schema, the description provides the full return shape, all parameter semantics, pagination notes, filtering limitations, error behavior, and data normalization details. Given the API's complexity and the absence of an output schema, the description is complete enough for an agent to invoke the tool correctly without additional external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial meaning beyond the schema: it maps each filter to the underlying FDIC field (state→PSTALP, failYear→FAILYR, cert→CERT), explains boundaries, defaults, enum behavior, and gives concrete examples. This materially reduces the chance of misusing parameters.

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?

The description clearly identifies the tool as returning historical FDIC-insured bank failures and assistance transactions, names the underlying endpoint, and explicitly links CERT to related tools (fdic_search_institutions, fdic_institution_financials). This differentiates it from sibling tools by dataset and primary entity key, and the return shape confirms what the agent will receive.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: it states there is NO name/city filter, that the FDIC search param is ignored, and that to find a specific bank's failure the agent should resolve its CERT via fdic_search_institutions. It also clarifies the stable entity key relationship, effectively routing the agent to the correct sibling tool when needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools