Skip to main content
Glama

FDIC BankFind MCP Server

Search FDIC Institutions

fdic_search_institutions
Read-onlyIdempotent

Use this when the user needs FDIC-insured institution search results by name, state, CERT, asset size, charter class, or regulatory status. Returns institution profile rows with pagination; use fdic://schemas/institutions for the full field catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return (1-10000, default: 20)
fieldsNoComma-separated list of FDIC field names to return. Leave empty to return all fields. Field names are ALL_CAPS (e.g., NAME, CERT, ASSET, DEP, STALP). Example: NAME,CERT,ASSET,DEP,STALP
offsetNoNumber of records to skip for pagination (default: 0)
filtersNoFDIC API filter using ElasticSearch query string syntax. Combine conditions with AND/OR, use quotes for multi-word values, and [min TO max] for ranges (* = unbounded). Common fields: NAME (institution name), STNAME (state name), STALP (two-letter state code), CERT (certificate number), ASSET (total assets in $thousands), ACTIVE (1=active, 0=inactive). Examples: STNAME:"California", ACTIVE:1 AND ASSET:[1000000 TO *], NAME:"Chase"
sort_byNoField name to sort results by. Example: ASSET, NAME, FAILDATE
sort_orderNoSort direction: ASC (ascending) or DESC (descending)ASC

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
totalYes
offsetYes
has_moreYes
truncatedNo
next_offsetNo
institutionsYes

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by disclosing that results are institution profile rows with pagination, and it directs to a field catalog via fdic://schemas/institutions. No contradictions with 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?

Two sentences with no filler. The purpose is front-loaded, followed by return type and a pointer to the field catalog. Every sentence earns its place.

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 output schema exists and annotations cover safety, the description effectively covers the tool's purpose, pagination behavior, and points to the full field catalog for complete parameter understanding. The search criteria mentioned align with the filterable fields.

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?

With 100% schema description coverage, the baseline is 3. The description does not add parameter-specific detail, but the schema thoroughly documents each parameter with examples and defaults. The description's mention of search criteria maps to the filters parameter but does not enhance beyond schema.

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 opens with 'Use this when the user needs FDIC-insured institution search results' and enumerates specific search criteria (name, state, CERT, asset size, charter class, regulatory status). This clearly specifies the verb+resource+scope and distinguishes it from sibling tools like fdic_get_institution (likely single-record) and fdic_search_financials.

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?

It provides explicit trigger conditions ('Use this when...') and notes pagination and the schema reference. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of a 5.

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.

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