FDIC BankFind MCP Server

Get Failure Details by Certificate Number

fdic_get_institution_failure

Read-onlyIdempotent

Retrieves failure details (date, resolution type, cost, acquirer) for a failed institution using its FDIC Certificate Number. Returns found: false if the institution did not fail.

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, cost, 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.

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.2/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds valuable non-obvious behavior: it responds with `found: false` for non-failed institutions, which clarifies edge-case handling beyond what annotations provide.

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 two sentences, front-loaded with the usage condition and followed by return behavior. No wasted words, and every sentence adds value.

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?

Given the tool's simplicity, an output schema exists, and annotations cover safety, the description is complete enough. It explains the core use case and the not-found behavior, which are the main contextual gaps.

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 coverage is 100%, so the baseline is 3. The description mentions 'CERT' and 'failure record' but does not add significant meaning beyond the schema's existing parameter descriptions for `cert` and `fields`.

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 states the tool's purpose: retrieving a specific failure record for a known CERT. It distinguishes from siblings like fdic_get_institution (general institution data) and fdic_search_failures (search across failures) by focusing on the direct lookup use case.

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?

The description explicitly states when to use it: 'when the user knows the CERT of a failed institution and needs its specific failure record.' It also implies when not to use it (if the institution did not fail) but does not name alternative tools or provide explicit exclusions.

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