Skip to main content
Glama

KeyVex

get_bank_financials

Read-only

Returns quarterly financials for every FDIC-insured US bank — FDIC BankFind Suite (RIS) data derived from Call Reports, one record per (bank, quarter-end) from 1984 to the present. Covers ~4,400 active institutions per modern quarter, most of which never file with the SEC — this is the banking-sector complement to get_fundamentals. Use this when the user asks about: a specific bank's assets / deposits / profitability / capital ratios, bank league tables ('largest banks in Texas'), deposit flight or brokered-deposit reliance, nonperforming-asset trends, or to pair bank fundamentals with OCC/FDIC/Fed enforcement actions and CFPB complaints. Record shape: identity (cert = FDIC certificate number, the stable bank key; name/city/state), balance sheet in $ THOUSANDS (total_assets, total_deposits, equity_capital, net_loans_leases, securities, loan buckets, brokered_deposits, insured-deposit estimates), income statement in $ thousands (net_income, interest income/expense, noninterest income/expense, provisions), and FDIC-computed ratios in percent (roa, roe, net_interest_margin, efficiency_ratio, leverage_ratio, tier1_risk_based_ratio, cet1_ratio, total_risk_based_ratio, nonperforming_assets_ratio, net_chargeoffs_ratio, loans_to_core_deposits). CONVENTIONS (Call Report): income-statement items are YEAR-TO-DATE (Q3 net_income = nine months, not the quarter alone; Q4 = full year); ratios are FDIC's annualized computations; roe_quarterly is the single-quarter ROE. Balance-sheet items are point-in-time. Matching a bank: cert (FDIC certificate #) is exact and stable — resolve it once via a name substring query, then use cert for history. Banks are subsidiaries: 'JPMorgan Chase Bank, National Association' (cert 628) is the insured bank, not the NYSE-listed holding company — for the parent's SEC financials use get_fundamentals. League tables: report_date='' + sort_by='total_assets' (e.g., report_date '2026-03-31'). Quarter-ends are 03-31 / 06-30 / 09-30 / 12-31. Latest quarter fills in progressively for ~60 days after quarter end as banks file. Pure-publisher: FDIC's numbers as published, no derived health scores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDirect lookup: '{cert}-{YYYY-MM-DD}' (e.g., '3511-2026-03-31'). Fastest path.
certNoFDIC certificate number (exact) — the stable bank identifier (e.g., 3511 = Wells Fargo Bank NA, 628 = JPMorgan Chase Bank NA).
nameNoCase-insensitive substring against the institution name (e.g., 'silicon valley', 'first republic').
limitNoMaximum records to return. Default 50, max 500.
sinceNoreport_date lower bound (YYYY-MM-DD inclusive).
stateNoTwo-letter state code (exact, e.g., 'CA', 'TX').
untilNoreport_date upper bound (YYYY-MM-DD inclusive).
sort_byNoDefault report_date. total_assets requires an exact report_date filter (league-table mode).
sort_orderNoDefault: desc.
report_dateNoExact quarter-end (YYYY-MM-DD: 03-31 / 06-30 / 09-30 / 12-31). Combine with sort_by='total_assets' for league tables.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/destructive/openWorld, and the description adds substantial context beyond them: Call Report provenance, ~4,400 institutions and 1984-present coverage, the YTD income-statement convention, FDIC-annualized ratios, the ~60-day progressive fill for the latest quarter, and the 'pure-publisher, no derived health scores' caveat.

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?

Front-loads purpose and is well-organized under labeled sections (CONVENTIONS, Matching a bank, League tables), with each section carrying usable content. It is dense and long, but almost every sentence earns its place; minor trimming would still be possible.

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?

No output schema exists, and the description fully covers the return shape (identity, balance sheet in $ thousands, income statement, FDIC ratios) plus conventions and key-resolution guidance. An agent has everything needed to call 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 coverage is 100%, so the baseline is 3, but the description adds real workflow meaning: cert is the exact stable key to resolve once via a name substring, the report_date + sort_by='total_assets' league-table recipe, and valid quarter-end formats. It does not add syntax beyond the schema, so it stops short of 5.

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?

States a specific verb and resource ('Returns quarterly financials for every FDIC-insured US bank') with scope and provenance, and explicitly distinguishes itself from the sibling get_fundamentals as 'the banking-sector complement.' An agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit when-to-use list (assets/deposits/profitability/capital ratios, league tables, deposit flight, NPA trends, pairing with enforcement/complaints) and names the alternative (get_fundamentals) plus the condition that selects it (parent holding company SEC financials).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources