Skip to main content
Glama
jflamb

FDIC BankFind MCP Server

by jflamb

Search FDIC Institutions

fdic_search_institutions
Read-onlyIdempotent

Search FDIC-insured banks and savings institutions using filters for location, asset size, charter class, and regulatory status to find financial institution data.

Instructions

Search for FDIC-insured financial institutions (banks and savings institutions) using flexible filters.

Returns institution profile data including name, location, charter class, asset size, deposit totals, profitability metrics, and regulatory status.

Common filter examples:

  • By state: STNAME:"California"

  • Active banks only: ACTIVE:1

  • Large banks: ASSET:[10000000 TO *] (assets in $thousands)

  • By bank class: BKCLASS:N (national bank), BKCLASS:SM (state member bank), BKCLASS:NM (state non-member)

  • By name: NAME:"Wells Fargo"

  • Commercial banks: CB:1

  • Savings institutions: MUTUAL:1

  • Recently established: ESTYMD:[2010-01-01 TO *]

Charter class codes (BKCLASS): N = National commercial bank (OCC-supervised) SM = State-chartered, Federal Reserve member NM = State-chartered, non-member (FDIC-supervised) SB = Federal savings bank (OCC-supervised) SA = State savings association OI = Insured branch of foreign bank

Key returned fields:

  • CERT: FDIC Certificate Number (unique ID)

  • NAME: Institution name

  • CITY, STALP (two-letter state code), STNAME (full state name): Location

  • ASSET: Total assets ($thousands)

  • DEP: Total deposits ($thousands)

  • BKCLASS: Charter class code (see above)

  • ACTIVE: 1 if currently active, 0 if inactive

  • ROA, ROE: Profitability ratios

  • OFFICES: Number of branch offices

  • ESTYMD: Establishment date (YYYY-MM-DD)

  • REGAGNT: Primary federal regulator (OCC, FRS, FDIC)

Args:

  • filters (string, optional): ElasticSearch query filter

  • fields (string, optional): Comma-separated field names

  • limit (number): Records to return, 1-10000 (default: 20)

  • offset (number): Pagination offset (default: 0)

  • sort_by (string, optional): Field to sort by

  • sort_order ('ASC'|'DESC'): Sort direction (default: 'ASC')

Prefer concise human-readable summaries or tables when answering users. Structured fields are available for totals, pagination, and institution records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNoFDIC 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"
fieldsNoComma-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
limitNoMaximum number of records to return (1-10000, default: 20)
offsetNoNumber of records to skip for pagination (default: 0)
sort_byNoField name to sort results by. Example: ASSET, NAME, FAILDATE
sort_orderNoSort direction: ASC (ascending) or DESC (descending)ASC

Implementation Reference

  • The handler function that executes the fdic_search_institutions tool logic.
    async (params) => {
      try {
        const response = await queryEndpoint(ENDPOINTS.INSTITUTIONS, params);
        const records = extractRecords(response);
        const pagination = buildPaginationInfo(
          response.meta.total,
          params.offset ?? 0,
          records.length,
        );
        const output = { ...pagination, institutions: records };
        const text = truncateIfNeeded(
          formatSearchResultText("institutions", records, pagination, [
            "CERT",
            "NAME",
            "CITY",
            "STALP",
            "ASSET",
            "ACTIVE",
          ]),
          CHARACTER_LIMIT,
          "Request fewer fields, narrow your filters, or paginate with limit/offset.",
        );
        return {
          content: [{ type: "text", text }],
          structuredContent: output,
        };
      } catch (err) {
        return formatToolError(err);
      }
    },
  • The registration of the fdic_search_institutions tool.
      server.registerTool(
        "fdic_search_institutions",
        {
          title: "Search FDIC Institutions",
          description: `Search for FDIC-insured financial institutions (banks and savings institutions) using flexible filters.
    
    Returns institution profile data including name, location, charter class, asset size, deposit totals, profitability metrics, and regulatory status.
    
    Common filter examples:
      - By state: STNAME:"California"
      - Active banks only: ACTIVE:1
      - Large banks: ASSET:[10000000 TO *]  (assets in $thousands)
      - By bank class: BKCLASS:N (national bank), BKCLASS:SM (state member bank), BKCLASS:NM (state non-member)
      - By name: NAME:"Wells Fargo"
      - Commercial banks: CB:1
      - Savings institutions: MUTUAL:1
      - Recently established: ESTYMD:[2010-01-01 TO *]
    
    Charter class codes (BKCLASS):
      N = National commercial bank (OCC-supervised)
      SM = State-chartered, Federal Reserve member
      NM = State-chartered, non-member (FDIC-supervised)
      SB = Federal savings bank (OCC-supervised)
      SA = State savings association
      OI = Insured branch of foreign bank
    
    Key returned fields:
      - CERT: FDIC Certificate Number (unique ID)
      - NAME: Institution name
      - CITY, STALP (two-letter state code), STNAME (full state name): Location
      - ASSET: Total assets ($thousands)
      - DEP: Total deposits ($thousands)
      - BKCLASS: Charter class code (see above)
      - ACTIVE: 1 if currently active, 0 if inactive
      - ROA, ROE: Profitability ratios
      - OFFICES: Number of branch offices
      - ESTYMD: Establishment date (YYYY-MM-DD)
      - REGAGNT: Primary federal regulator (OCC, FRS, FDIC)
    
    Args:
      - filters (string, optional): ElasticSearch query filter
      - fields (string, optional): Comma-separated field names
      - limit (number): Records to return, 1-10000 (default: 20)
      - offset (number): Pagination offset (default: 0)
      - sort_by (string, optional): Field to sort by
      - sort_order ('ASC'|'DESC'): Sort direction (default: 'ASC')
    
    Prefer concise human-readable summaries or tables when answering users. Structured fields are available for totals, pagination, and institution records.`,
          inputSchema: CommonQuerySchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
        },
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description adds valuable behavioral context beyond annotations: it explains the return format ('institution profile data'), provides extensive examples of filter usage, documents key returned fields with explanations, and mentions pagination behavior. This significantly enhances the agent's understanding of how to interact with the tool effectively.

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 well-structured and efficiently organized: it starts with the core purpose, then describes returns, provides extensive filter examples with explanations, documents key fields, lists parameters, and ends with output formatting guidance. Every sentence adds value—there's no redundant or unnecessary information—and the information is front-loaded for quick comprehension.

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?

Given the tool's complexity (6 parameters, no output schema), the description provides excellent contextual completeness. It thoroughly explains what the tool does, how to use filters with detailed examples, what data is returned, and how to format outputs. Combined with comprehensive annotations and a fully described schema, this gives the agent everything needed 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 schema already fully documents all 6 parameters. The description adds some semantic context by providing common filter examples that illustrate how to use the 'filters' parameter and listing key returned fields that relate to the 'fields' parameter. However, most parameter semantics are already covered in the schema, so this provides only marginal additional value.

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: 'Search for FDIC-insured financial institutions (banks and savings institutions) using flexible filters.' It specifies the verb ('search'), resource ('FDIC-insured financial institutions'), and scope ('banks and savings institutions'), and distinguishes itself from siblings by focusing on general institution search rather than specific aspects like failures, financials, or demographics.

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 provides clear context for when to use this tool (searching institutions with flexible filters) and mentions 'Prefer concise human-readable summaries or tables when answering users,' which offers output formatting guidance. However, it doesn't explicitly state when to use this tool versus specific sibling tools like fdic_search_financials or fdic_search_failures, nor does it provide exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jflamb/fdic-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server