FDIC BankFind MCP Server

Get Failure Details by Certificate Number

fdic_get_institution_failure

Read-onlyIdempotent

Retrieve a failed institution's record using its FDIC Certificate Number. Returns failure date, resolution type, estimated DIF cost, and acquirer, or indicates when no failure occurred.

Instructions

Use this when the user knows the CERT of a failed institution and needs its specific failure record. Returns failure details (date, resolution type, estimated DIF cost in the COST field, acquirer); responds with found: false if the institution did not fail.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cert`	Yes	FDIC Certificate Number — the unique identifier for an institution
`fields`	No	Comma-separated list of fields to return

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv3.0.1Sep 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / cert / maximum
```
Added value: +9007199254740991
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedv1.26.0May 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv1.1.3Mar 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral details beyond those annotations: the specific returned failure fields (date, resolution type, DIF cost in COST field, acquirer) and the `found: false` response for non-failed institutions.

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?

Two compact sentences with no filler. The usage trigger is front-loaded, followed by a concise list of returned data and the not-found behavior.

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 simple single-ID lookup with a rich output schema and safety annotations, the description covers the essential usage trigger, key return fields, and no-result behavior. Nothing critical is missing for an agent to invoke 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 parameters are already well documented. The description adds modest semantic context by linking CERT to a failed institution and noting the COST output field, but it doesn't add meaning beyond the schema for the parameters themselves.

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 names a specific verb ('get'), a specific resource ('failure record'), and the key required identifier (CERT). It clearly distinguishes this from general institution or search tools by limiting scope to failed institutions' specific failure records.

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?

It explicitly states when to use the tool: when the user knows the CERT and needs a specific failure record. It does not explicitly name an alternative like 'use fdic_search_failures when the CERT is unknown,' so it falls just short of full exclusion guidance.

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