Skip to main content
Glama
cliwant

mcp-sam-gov

fdic_institution_history

Read-only

Retrieve FDIC-insured banks' structural-change events — mergers, failures, name/location changes, and branch activity — filtered by certificate, change code, state, or year, with merger lineage via acquirer/outgoing/surviving CERTs.

Instructions

Institution-level STRUCTURAL-CHANGE event log for FDIC-insured banks (keyless; api.fdic.gov/banks/history) — mergers, absorptions, consolidations, failures, name/location/charter/regulator changes, branch open/close, trust-power grants & FRS-membership. CERT-linked merger lineage: each row carries acquiring/outgoing/surviving institution CERT + name, linking to fdic_search_institutions / fdic_bank_failures. Filters (all optional, AND-combined): cert (→CERT, PRIMARY lookup), changeCode (→CHANGECODE; e.g. 223=merger, 211=failure, 721=branch closing), effYear (→EFFYEAR), state (2-letter → PSTALP — NOTE: /history uses PSTALP, NOT STALP). limit (≤1000), offset (≤100000), sortBy (EFFDATE/PROCDATE/CHANGECODE/TRANSNUM), sortOrder. Returns { history:[{ cert, instName, state, changeCode, changeDescription, effectiveDate, processDate, effYear, transNum, acquirerCert, acquirerName, outgoingCert, outgoingName, survivingCert, survivingName, id }] }. NO name/city filter — FDIC /history search returns 0 for INSTNAME (a false-empty); resolve CERT via fdic_search_institutions first. HONESTY: totalAvailable is EXACT meta.total; changeDescription is FDIC's CHANGECODE_DESC verbatim (changeCode is authoritative — never hand-mapped); effectiveDate/processDate normalized to ISO YYYY-MM-DD (unrecognized → surfaced raw); acquirer/outgoing/surviving CERTs null on non-merger events (null-never-0); ONLY honest empty is meta.total:0/data:[] → complete:true/total:0; any other envelope THROWS (never fake-empty). 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 — the PRIMARY lookup). Resolve a bank's CERT via fdic_search_institutions. e.g. 3510 → Bank of America's 13,794-row structural-change history.
limitNoRows per page, 1..1000, default 100.
stateNoFilter by 2-letter US state code (uppercase; → PSTALP filter — the /history state field is PSTALP, NOT STALP). e.g. 'CA'.
offsetNo0-based row offset for pagination, 0..100000, default 0.
sortByNoSort field (allowlisted enum; default EFFDATE = effective date). An unknown field is rejected before fetch.
effYearNoFilter by the year the structural change took effect (→ EFFYEAR filter). 1782..current UTC year (1782 = the oldest observed EFFYEAR).
sortOrderNoSort direction, default DESC (newest structural change first).
changeCodeNoFilter by FDIC structural-change code (→ CHANGECODE filter). e.g. 223 = Merger (Without Assistance), 211 = Failure (Whole Institution), 721 = Branch Closing, 520 = Change in Physical Location, 110 = New Institution. Each row also carries FDIC's own changeDescription (CHANGECODE_DESC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only provide readOnlyHint and openWorldHint, so the description carries the behavioral burden and exceeds it: keyless access, exact meta.total semantics, null-never-0 for non-merger CERTs, date normalization rules, authoritative changeCode behavior, and throw-on-unexpected-envelope handling. The only-honest-empty condition is spelled out precisely, which is exactly the disclosure an agent needs.

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 description is front-loaded with purpose and the event-type scope, followed by filters, response shape, and critical caveats. It is long and repeats some schema details such as example change codes and sort defaults, but the density is justified by the API's unusual behavioral traps.

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?

For a keyless read-only API with no output schema, this description covers the endpoint, primary lookup path, all filter mappings, return field names, pagination and sorting options, date normalization, and exact empty/error behavior. An agent can correctly construct and interpret a call without external documentation.

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

Parameters4/5

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

Schema coverage is 100% with already detailed per-parameter descriptions, so the baseline is 3. The description adds cross-cutting semantic guidance: all filters are optional and AND-combined, the PSTALP-vs-STALP trap, the absence of name/city filtering with a false-empty warning, and the intended CERT-first lookup strategy.

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 clearly it is an institution-level structural-change event log for FDIC-insured banks and enumerates the event types: mergers, absorptions, failures, name/location/charter changes, and more. This distinguishes it from sibling FDIC tools such as fdic_bank_failures and fdic_institution_financials without ambiguity.

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?

Explicitly instructs that name/city lookups are not supported and that CERT must be resolved via fdic_search_institutions first, warning that the FDIC /history search returns a false-empty for INSTNAME. It also links to fdic_bank_failures for related lineage but does not systematically contrast this tool with every FDIC sibling, so it stops short of a full when-to-use matrix.

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