FDIC BankFind MCP Server

Search Annual Financial Summary Data

fdic_search_summary

Read-onlyIdempotent

Retrieve annual financial-summary snapshots for FDIC-insured institutions, including assets, deposits, ROA, ROE, and offices, filtered by certificate number and year.

Instructions

Use this when the user wants annual financial-summary snapshots (assets, deposits, ROA, ROE, offices) for FDIC-insured institutions, filtered by CERT and/or year. See fdic://schemas/summary for the full field catalog.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cert`	No	Filter by FDIC Certificate Number
`year`	No	Filter by specific year (e.g., 2022)
`limit`	No	Maximum number of records to return (1-10000, default: 20)
`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
`offset`	No	Number of records to skip for pagination (default: 0)
`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"
`sort_by`	No	Field name to sort results by. Example: ASSET, NAME, FAILDATE
`sort_order`	No	Sort direction: ASC (ascending) or DESC (descending)	ASC

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 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
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / year / 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"
```
- addedOutput schema / properties / count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / count / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / next_offset / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / next_offset / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / offset / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / summary / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / total / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total / minimum
```
Added value: +-9007199254740991
```

Changed1 schema field changedv1.26.0May 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "next_offset": {
+      "type": "integer"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "summary": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "total",
+    "offset",
+    "count",
+    "has_more",
+    "summary"
+  ],
+  "type": "object"
+}

First observedv1.1.3Mar 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful context about the data scope and points to a full field catalog (fdic://schemas/summary), but does not disclose behaviors like pagination defaults or result limits beyond what the schema already provides. With annotations in place, this is adequate but not exceptional.

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 tool's use case, and ends with a useful pointer to the full field schema. Every word earns its place; there is no redundancy or filler.

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?

With an output schema, 100% parameter coverage, and strong annotations, the description covers the core purpose and main filter dimensions. It does not disambiguate from the similarly named fdic_search_financials, which is the main gap for an otherwise complete tool definition.

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 hint that results are 'filtered by CERT and/or year', which aligns with the schema, but it provides no additional meaning for limit, offset, fields, filters, sort_by, or sort_order beyond their already-detailed schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific verb ('search'), a specific resource ('annual financial-summary snapshots'), and the key data fields (assets, deposits, ROA, ROE, offices). It does not explicitly contrast itself with the sibling fdic_search_financials, which could be confused, so it falls just short of full sibling differentiation.

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...' and clearly specifies the conditions (annual financial-summary snapshots, filtered by CERT/year). It provides solid when-to-use context but gives no when-not-to-use guidance or explicit alternative tools, such as pointing to fdic_search_financials for quarterly data.

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