Skip to main content
Glama

FDIC BankFind MCP Server

by io.github.jflamb

Regional Economic Context

fdic_regional_context
Read-onlyIdempotent

Overlay macro/regional economic data on a bank's geographic context. Uses FRED (Federal Reserve Economic Data) for state unemployment, national unemployment, and federal funds rate. Provides trend analysis and narrative context for bank performance assessment. Gracefully degrades if FRED API is unavailable.

Output includes:

  • State and national unemployment rates with trend analysis

  • Federal funds rate and rate environment classification

  • Narrative assessment of macro conditions for bank performance

  • Structured JSON for programmatic consumption

NOTE: Requires FRED_API_KEY environment variable for reliable data access. Degrades gracefully without it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certNoFDIC Certificate Number — auto-detects state from institution record.
stateNoTwo-letter state abbreviation (e.g., TX). Alternative to cert-based lookup.
repdteNoReference report date (YYYYMMDD). FRED data fetched for 2 years before this date.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses graceful degradation when FRED is unavailable, the API key dependency, and that it produces both narrative and structured JSON output. This provides valuable behavioral context not covered by annotations.

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-structured with a clear opening sentence, a concise output list, and a crucial note about FRED_API_KEY. Every sentence contributes useful information with no redundancy, and the most important purpose is front-loaded.

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 presence of a rich output schema and strong annotations, the description covers the essential additional context: purpose, data source, outputs, degradation behavior, and environment requirement. It is sufficiently complete for a tool with three optional parameters.

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?

Schema coverage is 100% with parameter descriptions already provided. The description adds some context by naming the data sources (FRED) and outputs (state/national unemployment, federal funds rate), but doesn't deeply elaborate on how each parameter maps to those outputs, so baseline 3 is appropriate.

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 overlays macroeconomic/regional data on a bank's geographic context using FRED, with specific indicators (state/national unemployment, federal funds rate). This verb+resource+scope clearly distinguishes it from siblings like fdic_analyze_bank_health or fdic_franchise_footprint.

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 implies use for bank performance assessment when macro context is needed, and explicitly mentions the FRED API key requirement. However, it doesn't name alternatives or state when not to use this tool explicitly, so it misses the full 'when/when-not' guidance.

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

All FDIC BankFind MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation1/5

Several tools have overlapping purposes, including exact duplicates: fdic_fetch/fetch and fdic_search/search. Analytical tools also overlap (analyze_bank_health, ubpr_analysis, detect_risk_signals), making it hard for an agent to distinguish them.

Naming Consistency2/5

Most tools follow a fdic_verb_noun pattern, but two tools (fetch, search) lack the fdic_ prefix, breaking consistency. The verb style varies (get, search, analyze, compare, detect) but the prefix inconsistency is the main issue.

Tool Count2/5

At 29 tools, the server is over the typical limit and includes redundant pairs that inflate the count. The broad FDIC domain justifies many tools, but the duplicates indicate poor scoping.

Completeness4/5

The server covers all major FDIC data resources: institutions, failures, financials, branches, history, demographics, SOD, and summary, plus analytical tools. No major gaps are evident for its read-only data and analysis purpose.

Resources