Skip to main content
Glama

FDIC BankFind MCP Server

Search Institution Locations / Branches

fdic_search_locations
Read-onlyIdempotent

Use this when the user wants branch/office locations for FDIC-insured institutions, filtered by CERT, state, city, county, metro area, or branch type. Returns address, coordinates, branch number, and service-type rows; see fdic://schemas/locations for the full field catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certNoFilter by FDIC Certificate Number to get all branches of a specific institution
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
locationsYes
truncatedNo
next_offsetNo

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by stating what the tool returns (address, coordinates, branch number, service-type rows) and referring to a schema for the full field catalog, providing useful behavioral context beyond the 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 two sentences, front-loaded with usage context, and contains no filler. Every sentence contributes: the first specifies when to use and filter dimensions; the second details return types and points to a schema for more detail.

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?

The tool is a search/lookup operation with 7 parameters, an output schema, and good annotations. The description covers purpose, return types, and schema reference. It doesn't mention pagination or caveats, but the schema covers those, making the description sufficiently complete for an agent to select and invoke the tool 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?

Input schema description coverage is 100%, so the baseline is 3. The description adds semantic value by naming filter dimensions (CERT, state, city, county, metro area, branch type) that are not all explicitly listed in the schema's common fields, helping the agent construct filter expressions.

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 purpose: retrieving branch/office locations for FDIC-insured institutions with specific filter dimensions (CERT, state, city, county, metro area, branch type). It distinguishes from sibling search tools by focusing on locations/branches and listing return types (address, coordinates, branch number, service-type rows).

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 begins with 'Use this when the user wants branch/office locations...' which is an explicit usage context. It does not explicitly mention when not to use or name alternatives, but the purpose is narrow enough to differentiate from sibling search tools like fdic_search_institutions or fdic_search_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.

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