Skip to main content
Glama
jflamb

FDIC BankFind MCP Server

by jflamb

Search Institution Financial Data

fdic_search_financials
Read-onlyIdempotent

Search quarterly financial data for FDIC-insured banks to analyze balance sheets, income statements, capital levels, and performance ratios using over 1,100 variables.

Instructions

Search quarterly financial (Call Report) data for FDIC-insured institutions. Covers over 1,100 financial variables reported quarterly.

Returns balance sheet, income statement, capital, and performance ratio data from FDIC Call Reports.

Common filter examples:

  • Financials for a specific bank: CERT:3511

  • By report date: REPDTE:20231231

  • High-profit banks in Q4 2023: REPDTE:20231231 AND ROA:[1.5 TO *]

  • Large banks most recent: ASSET:[10000000 TO *]

  • Negative net income: NETINC:[* TO 0]

Key returned fields:

  • CERT: FDIC Certificate Number

  • REPDTE: Report Date — the last day of the quarterly reporting period (YYYYMMDD)

  • ASSET: Total assets ($thousands)

  • DEP: Total deposits ($thousands)

  • DEPDOM: Domestic deposits ($thousands)

  • INTINC: Total interest income ($thousands)

  • EINTEXP: Total interest expense ($thousands)

  • NETINC: Net income ($thousands)

  • ROA: Return on assets (%)

  • ROE: Return on equity (%)

  • NETNIM: Net interest margin (%)

Args:

  • cert (number, optional): Filter by institution CERT number

  • repdte (string, optional): Report Date in YYYYMMDD format (quarter-end dates: 0331, 0630, 0930, 1231)

  • filters (string, optional): Additional ElasticSearch query filters

  • fields (string, optional): Comma-separated field names (the full set has 1,100+ fields)

  • limit (number): Records to return (default: 20)

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

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

  • sort_order ('ASC'|'DESC'): Sort direction (default: 'DESC' recommended for most recent first)

Prefer concise human-readable summaries or tables when answering users. Structured fields are available for totals, pagination, and quarterly financial 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: DESC (descending, default for most recent first) or ASC (ascending)DESC
certNoFilter by FDIC Certificate Number to get financials for a specific institution
repdteNoFilter 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).

Implementation Reference

  • The handler function for fdic_search_financials tool, which queries the FDIC financials endpoint, formats the results, and handles pagination.
    async ({ cert, repdte, ...params }) => {
      try {
        const response = await queryEndpoint(ENDPOINTS.FINANCIALS, {
          ...params,
          filters: buildFilterString({
            cert,
            dateField: "REPDTE",
            dateValue: repdte,
            rawFilters: params.filters,
          }),
        });
        const records = extractRecords(response);
        const pagination = buildPaginationInfo(
          response.meta.total,
          params.offset ?? 0,
          records.length,
        );
        const output = { ...pagination, financials: records };
        const text = truncateIfNeeded(
          formatSearchResultText("financial records", records, pagination, [
            "CERT",
            "NAME",
            "REPDTE",
            "ASSET",
            "DEP",
            "NETINC",
          ]),
          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 tool registration for fdic_search_financials, including its metadata, description, input schema, and handler.
      server.registerTool(
        "fdic_search_financials",
        {
          title: "Search Institution Financial Data",
          description: `Search quarterly financial (Call Report) data for FDIC-insured institutions. Covers over 1,100 financial variables reported quarterly.
    
    Returns balance sheet, income statement, capital, and performance ratio data from FDIC Call Reports.
    
    Common filter examples:
      - Financials for a specific bank: CERT:3511
      - By report date: REPDTE:20231231
      - High-profit banks in Q4 2023: REPDTE:20231231 AND ROA:[1.5 TO *]
      - Large banks most recent: ASSET:[10000000 TO *]
      - Negative net income: NETINC:[* TO 0]
    
    Key returned fields:
      - CERT: FDIC Certificate Number
      - REPDTE: Report Date — the last day of the quarterly reporting period (YYYYMMDD)
      - ASSET: Total assets ($thousands)
      - DEP: Total deposits ($thousands)
      - DEPDOM: Domestic deposits ($thousands)
      - INTINC: Total interest income ($thousands)
      - EINTEXP: Total interest expense ($thousands)
      - NETINC: Net income ($thousands)
      - ROA: Return on assets (%)
      - ROE: Return on equity (%)
      - NETNIM: Net interest margin (%)
    
    Args:
      - cert (number, optional): Filter by institution CERT number
      - repdte (string, optional): Report Date in YYYYMMDD format (quarter-end dates: 0331, 0630, 0930, 1231)
      - filters (string, optional): Additional ElasticSearch query filters
      - fields (string, optional): Comma-separated field names (the full set has 1,100+ fields)
      - limit (number): Records to return (default: 20)
      - offset (number): Pagination offset (default: 0)
      - sort_by (string, optional): Field to sort by
      - sort_order ('ASC'|'DESC'): Sort direction (default: 'DESC' recommended for most recent first)
    
    Prefer concise human-readable summaries or tables when answering users. Structured fields are available for totals, pagination, and quarterly financial records.`,
          inputSchema: FinancialQuerySchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
        },
  • The input schema validation for the fdic_search_financials tool using Zod.
    const FinancialQuerySchema = CommonQuerySchema.extend({
      sort_order: z
        .enum(["ASC", "DESC"])
        .default("DESC")
        .describe(
          "Sort direction: DESC (descending, default for most recent first) or ASC (ascending)",
        ),
      cert: z
        .number()
        .int()
        .positive()
        .optional()
        .describe(
          "Filter by FDIC Certificate Number to get financials for a specific institution",
        ),
      repdte: z
        .string()
        .optional()
        .describe(
          "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).",
        ),
    });
Behavior4/5

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

While annotations already indicate read-only, open-world, idempotent, and non-destructive behavior, the description adds valuable context about the data source (FDIC Call Reports), quarterly reporting nature, and the recommendation to prefer concise human-readable summaries. It also mentions the tool returns structured fields for totals, pagination, and quarterly records.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections covering purpose, data scope, filter examples, key fields, and usage guidance. While comprehensive, some sentences could be more concise (e.g., the filter examples section is quite detailed). The information is front-loaded with the core purpose stated first.

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 complexity (8 parameters, financial data domain) and lack of output schema, the description provides substantial context about data coverage, key fields, and usage patterns. The filter examples and field explanations help compensate for the missing output schema. However, it could better explain the relationship to sibling tools.

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?

With 100% schema description coverage, the schema already thoroughly documents all 8 parameters. The description adds some value by listing key returned fields and providing filter examples, but doesn't significantly enhance parameter understanding beyond what the schema provides. The baseline of 3 is appropriate given the comprehensive schema.

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 searches quarterly financial (Call Report) data for FDIC-insured institutions, specifying it covers over 1,100 financial variables. It distinguishes from siblings by focusing on financial data rather than demographics, failures, or other institution attributes.

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 about when to use this tool (for financial data searches) and includes common filter examples that illustrate typical use cases. However, it doesn't explicitly state when to choose this over sibling tools like fdic_search_institutions or fdic_search_demographics.

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