FDIC BankFind MCP Server

Search Institution Financial Data

fdic_search_financials

Read-onlyIdempotent

Retrieve quarterly Call Report data for FDIC-insured institutions, including balance sheets, income statements, and performance ratios, by filtering on certificate number, report date, or other ElasticSearch fields.

Instructions

Use this when the user wants quarterly Call Report data (balance sheet, income, capital, performance ratios) for FDIC-insured institutions. Filter by CERT and/or REPDTE plus optional ElasticSearch filters. See fdic://schemas/financials for the full 1,100+ field catalog.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filters`	No	FDIC API filter using ElasticSearch query string syntax. Combine conditions with AND/OR, use quotes for multi-word values, and [min TO max] for ranges (* = unbounded). Common fields: NAME (institution name), STNAME (state name), STALP (two-letter state code), CERT (certificate number), ASSET (total assets in $thousands), ACTIVE (1=active, 0=inactive). Examples: STNAME:"California", ACTIVE:1 AND ASSET:[1000000 TO *], NAME:"Chase"
`fields`	No	Comma-separated list of FDIC field names to return. Leave empty to return all fields. Field names are ALL_CAPS (e.g., NAME, CERT, ASSET, DEP, STALP). Example: NAME,CERT,ASSET,DEP,STALP
`limit`	No	Maximum number of records to return (1-10000, default: 20)
`offset`	No	Number of records to skip for pagination (default: 0)
`sort_by`	No	Field name to sort results by. Example: ASSET, NAME, FAILDATE
`sort_order`	No	Sort direction: DESC (descending, default for most recent first) or ASC (ascending)	DESC
`cert`	No	Filter by FDIC Certificate Number to get financials for a specific institution
`repdte`	No	Filter by Report Date (REPDTE) in YYYYMMDD format (quarter-end: 0331, 0630, 0930, 1231). If omitted, returns all available dates (sorted most recent first).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`offset`	Yes
`count`	Yes
`has_more`	Yes
`next_offset`	No
`financials`	Yes
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.26.0May 1, 2026

changedInput schema / properties / repdte / description

Previous value: -"Filter by Report Date (REPDTE) in YYYYMMDD format. FDIC data is published quarterly on call report dates: March 31, June 30, September 30, and December 31. Example: 20231231 for Q4 2023. If omitted, returns all available dates (sorted most recent first by default)."New value: +"Filter by Report Date (REPDTE) in YYYYMMDD format (quarter-end: 0331, 0630, 0930, 1231). If omitted, returns all available dates (sorted most recent first)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "financials": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "ASSET": {
+            "type": "number"
+          },
+          "CERT": {
+            "type": "integer"
+          },
+          "DEP": {
+            "type": "number"
+          },
+          "EEFFR": {
+            "type": "number"
+          },
+          "IDT1CER": {
+            "type": "number"
+          },
+          "LNLSDEPR": {
+            "type": "number"
+          },
+          "NAME": {
+            "type": "string"
+          },
+          "NCLNLSR": {
+            "type": "number"
+          },
+          "NETINC": {
+            "type": "number"
+          },
+          "NIMY": {
+            "type": "number"
+          },
+          "REPDTE": {
+            "type": [
+              "string",
+              "number"
+            ]
+          },
+          "ROA": {
+            "type": "number"
+          },
+          "ROE": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "next_offset": {
+      "type": "integer"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "total",
+    "offset",
+    "count",
+    "has_more",
+    "financials"
+  ],
+  "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=true and destructiveHint=false, so the description's job is lighter. It adds useful context by specifying the data domain (quarterly Call Report data) and referencing the full field catalog. It doesn't contradict annotations, and no additional safety disclosure is needed given the optimistic annotations.

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 three sentences, front-loaded with the primary use case, followed by filtering guidance and a reference to the schema catalog. Every sentence provides distinct value with no redundancy or fluff.

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 complex tool with 1,100+ fields and an existing output schema, the description effectively covers the core purpose, key filters, and points to the schema for full field details. It doesn't need to explain return values since an output schema exists, and the description is sufficiently complete for an agent to select and invoke the tool 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 baseline is 3. The description adds a brief mention of 'Filter by CERT and/or REPDTE plus optional ElasticSearch filters,' which orients the user but doesn't provide additional syntax or meaning beyond the schema's already detailed parameter descriptions.

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 provides quarterly Call Report data (balance sheet, income, capital, performance ratios) for FDIC-insured institutions, using a specific verb ('wants') and resource. It distinguishes from siblings by focusing on financial data and explicitly mentions filtering by CERT and REPDTE, unlike institution-centric or demographic search tools.

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 opens with 'Use this when the user wants quarterly Call Report data,' giving clear when-to-use guidance. It also explains how to filter via CERT/REPDTE and optional ElasticSearch filters, but it does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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