Skip to main content
Glama
jflamb

FDIC BankFind MCP Server

by jflamb

Compare Bank Snapshot Trends

fdic_compare_bank_snapshots
Read-onlyIdempotent

Compare FDIC reporting snapshots across banks to rank growth, profitability, or efficiency changes. Batch roster lookup, financial snapshots, and demographics for analytical comparisons.

Instructions

Compare FDIC reporting snapshots across a set of institutions and rank the results by growth, profitability, or efficiency changes.

This tool is designed for heavier analytical prompts that would otherwise require many separate MCP calls. It batches institution roster lookup, financial snapshots, optional office-count snapshots, and can also fetch a quarterly time series inside the server.

Good uses:

  • Identify North Carolina banks with the strongest asset growth from 2021 to 2025

  • Compare whether deposit growth came with branch expansion or profitability improvement

  • Rank a specific cert list by ROA, ROE, asset-per-office, or deposit-to-asset changes

  • Pull a quarterly trend series and highlight inflection points, streaks, and structural shifts

Inputs:

  • state or certs: choose a geographic roster or provide a direct comparison set

  • start_repdte, end_repdte: Report Dates (REPDTE) in YYYYMMDD format — must be quarter-end dates (0331, 0630, 0930, 1231)

  • analysis_mode: snapshot or timeseries

  • institution_filters: optional extra institution filter when building the roster

  • active_only: default true

  • include_demographics: default true, adds office-count comparisons when available

  • sort_by: ranking field (default: asset_growth). All options: asset_growth, asset_growth_pct, dep_growth, dep_growth_pct, netinc_change, netinc_change_pct, roa_change, roe_change, offices_change, assets_per_office_change, deposits_per_office_change, deposits_to_assets_change

  • sort_order: ASC or DESC

  • limit: maximum ranked results to return

Returns concise comparison text plus structured deltas, derived metrics, and insight tags for each institution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoState name for the institution roster filter. Example: "North Carolina"
certsNoOptional list of FDIC certificate numbers to compare directly. Max 100.
institution_filtersNoAdditional institution-level filter used when building the comparison set. Example: BKCLASS:N or CITY:"Charlotte"
active_onlyNoLimit the comparison set to currently active institutions.
start_repdteNoStarting Report Date (REPDTE) in YYYYMMDD format. Must be a quarter-end date: March 31 (0331), June 30 (0630), September 30 (0930), or December 31 (1231). Example: 20210331 for Q1 2021. If omitted, defaults to the same quarter one year before end_repdte.
end_repdteNoEnding Report Date (REPDTE) in YYYYMMDD format. Must be a quarter-end date: March 31 (0331), June 30 (0630), September 30 (0930), or December 31 (1231). Must be later than start_repdte. Example: 20251231 for Q4 2025. If omitted, defaults to the most recent quarter-end date with published data (~90-day lag).
analysis_modeNoUse snapshot for two-point comparison or timeseries for quarterly trend analysis across the date range.snapshot
include_demographicsNoInclude office-count changes from the demographics dataset when available.
limitNoMaximum number of ranked comparisons to return.
sort_byNoComparison field used to rank institutions. Valid options: asset_growth, asset_growth_pct, dep_growth, dep_growth_pct, netinc_change, netinc_change_pct, roa_change, roe_change, offices_change, assets_per_office_change, deposits_per_office_change, deposits_to_assets_change.asset_growth
sort_orderNoSort direction for the ranked comparisons.DESC

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent, and openWorld hints. The description adds value by explaining it batches operations, returns structured deltas and insight tags, and describes behavior across modes. No contradiction.

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-organized into clear sections: purpose, use cases, inputs, returns. Every sentence adds value with no fluff. Concise yet comprehensive.

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 complexity (11 parameters, optional output schema), the description covers inputs, outputs, and use cases thoroughly. It explains both snapshot and timeseries modes, and the return format. No gaps.

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 coverage is 100% with good descriptions for each parameter. The description adds context by explaining which parameters are used for roster building, filtering, and sorting, and by listing sort_by options again. Minor redundancy but overall helpful.

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 explicitly states the tool compares FDIC snapshots and ranks by growth/profitability/efficiency. It distinguishes from siblings by noting it batches multiple MCP calls and includes optional office-count features.

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?

Good uses are clearly listed with examples (e.g., identifying banks with strongest asset growth). It explains when to use, but does not explicitly state when not to use or name alternatives, though the sibling list implies specialization.

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