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 to detect early warning risk signals using CAMELS proxy analysis, with severity-ranked output for critical, warning, and info indicators.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / certs / items / maximum
      Added value: +9007199254740991
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  2. Addedv1.22.0
  3. Removedv1.10.2
  4. Addedv1.23.1
  5. Removedv1.14.0
  6. Addedv1.7.3
  7. Removedv1.4.4
  8. Addedv1.2.11
  9. Removedv1.2.5
  10. Addedv1.2.10
  11. Removedv1.2.4
  12. Addedv1.29.0
  13. Removedv1.2.1
  14. Addedv1.25.1
  15. Removedv1.2.6
  16. Addedv1.4.6

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable context about the output shape ('signal-shaped, not assessment-shaped') and the proxy nature ('Public off-site analytical proxy — not official supervisory ratings'), which informs the agent about the tool's limitations beyond what annotations capture.

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 lists and clear sections. It front-loads the purpose and then details signal codes and modes. The length is justified by the complexity of the tool, and each section earns its place.

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 presence of an output schema (as indicated), the description does not need to explain return values. It covers the tool's purpose, modes, signal codes, severity levels, and limitations. It is complete for an agent to call the tool correctly, though it could potentially add more explicit exclusions relative to siblings.

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 parameters are already described. The description adds meaningful usage patterns by mapping modes to parameters (e.g., state for state-wide, certs for explicit list, asset_min/asset_max for asset-based) and clarifies the min_severity enum levels. This goes beyond the schema's field-level descriptions.

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 function: scanning FDIC-insured institutions for early warning risk signals using a specific engine. It differentiates from siblings by focusing on 'risk signals' and mentions the proxy engine, which distinguishes it from other analysis tools.

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 explicit guidance on how to use the three scan modes (state-wide, explicit list, asset-based) and which parameters to provide for each. It also implies a distinction from full assessments via 'signal-shaped, not assessment-shaped', though it does not name specific sibling alternatives.

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