Skip to main content
Glama
jflamb

FDIC BankFind MCP Server

by jflamb

Detect Risk Signals (Early Warning)

fdic_detect_risk_signals
Read-onlyIdempotent

Scan FDIC-insured institutions for early warning risk signals using the public_camels_proxy_v1 analytical engine. Supports state-wide, CERT list, or asset-based scans. Returns per-institution risk signals ranked by severity.

Instructions

Scan FDIC-insured institutions for early warning risk signals using the public_camels_proxy_v1 analytical engine.

Standardized signal codes with severity levels:

  • Critical: capital_undercapitalized (PCA breach), earnings_loss (ROA < 0), reserve_coverage_low (< 50%)

  • Warning: capital_buffer_erosion, credit_deterioration, credit_deterioration_trending, earnings_pressure, margin_compression, funding_stress, funding_ltd_stretched, rate_risk_proxy_elevated, wholesale_funding_elevated

  • Info: merger_distorted_trend, stale_reporting_period

Three scan modes:

  • State-wide: provide state to scan all active institutions

  • Explicit list: provide certs (up to 50)

  • Asset-based: provide asset_min/asset_max

Output: Per-institution risk signals ranked by severity count. The proxy engine drives signal generation internally; the output is signal-shaped, not assessment-shaped.

NOTE: Public off-site analytical proxy — not official supervisory ratings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoScan all active institutions in this state.
certsNoSpecific CERTs to scan (max 50).
asset_minNoMinimum total assets ($thousands) filter.
asset_maxNoMaximum total assets ($thousands) filter.
repdteNoReport Date (YYYYMMDD). Defaults to the most recent quarter.
min_severityNoMinimum severity level to include in results (default: warning).warning
quartersNoPrior quarters to fetch for trend analysis (default 4).
limitNoMax flagged institutions to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations indicate read-only and idempotent. Description adds context: public off-site proxy, not official ratings, engine type, and output format. No contradictions.

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?

Well-structured with bullet points and sections, but slightly verbose. Front-loaded with main verb and purpose.

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?

Covers all key aspects: signal codes, severity, scan modes, and notes on proxy nature. Output schema handles return values. Adequate for complexity.

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?

All parameters have schema descriptions. The description adds high-level context (modes) but does not significantly enhance per-parameter meaning beyond the schema.

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?

Description clearly states it scans FDIC-insured institutions for early warning risk signals using a specific engine, lists signal codes and scan modes. It is specific but does not explicitly differentiate from sibling tools like fdic_analyze_bank_health.

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

Usage Guidelines3/5

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

Describes three scan modes (state-wide, explicit list, asset-based) and provides context for when to use each. However, it lacks explicit 'when not to use' guidance or comparison with alternatives.

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