FDIC BankFind MCP Server

Search Institution Locations / Branches

fdic_search_locations

Read-onlyIdempotent

Search FDIC-insured branch locations by CERT, state, city, county, metro area, or branch type. Returns addresses, coordinates, and service details.

Instructions

Use this when the user wants branch/office locations for FDIC-insured institutions, filtered by CERT, state, city, county, metro area, or branch type. Returns address, coordinates, branch number, and service-type rows; see fdic://schemas/locations for the full field catalog.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cert`	No	Filter by FDIC Certificate Number to get all branches of a specific institution
`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
`has_more`	Yes
`locations`	Yes
`truncated`	No
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 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
```
- 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 / locations / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- 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 / 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"
+    },
+    "locations": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_offset": {
+      "type": "integer"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "total",
+    "offset",
+    "count",
+    "has_more",
+    "locations"
+  ],
+  "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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations by naming the returned content categories: address, coordinates, branch number, and service-type rows, plus a pointer to the full field catalog.

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 key usage condition, and contains no filler. Every clause either refines the tool's scope, describes the output, or points to authoritative schema documentation.

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 read-only search tool with detailed input schemas, rich annotations, and an output schema, the description is complete. It covers when to use the tool, what it returns, and how to get full field details, so an agent has enough to select and invoke it correctly.

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 description coverage is 100%, so the bar for adding value is moderate. The description still adds meaning by naming additional filter dimensions such as city, county, metro area, and branch type that are not explicitly listed in the filters parameter examples, helping the agent understand the breadth of the filters string.

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 clearly states the tool searches for branch/office locations of FDIC-insured institutions and lists filter dimensions. It is specific about the resource type, but it does not explicitly distinguish itself from sibling tools like fdic_search_sod or fdic_search_institutions, so it stops short of full 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 opening 'Use this when the user wants branch/office locations...' gives clear, actionable guidance for when to select this tool. It does not mention alternatives or when-not-to-use scenarios, but the when condition is explicit and direct.

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