Skip to main content
Glama

Bank Directory

banks
Read-onlyIdempotent

Directory of all FDIC-insured banks with identity + headline figures. (Source: FFIEC + FDIC.) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "banks"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName search, case-insensitive. Alone, it uses the site's name matcher, which forgives punctuation, spacing and common abbreviations; with state or tier it matches any part of the legal name.
sortNoSort order: total_assets (default), legal_name, hq_state, established, cet1_ratio, roa, npl_ratio.
tierNoAsset-size tier, exactly one of: '1: >= $250B', '2: $100B-250B', '3: $10B-100B', '4: $1B-10B', '5: $100M-1B', '6: < $100M'.
limitNoMax rows to return.
stateNoTwo-letter state filter.
offsetNoPagination offset.
min_assetsNoMinimum total assets ($000s).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety behavior is covered. The description adds genuinely useful context beyond them: the data provenance (FFIEC + FDIC) and, critically, the unit conventions — dollar amounts in thousands and ratios as percentages — which would otherwise cause misinterpretation of returned figures.

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 short sentences, front-loaded with what the tool returns, followed by sourcing and unit conventions. No filler, no restatement of the name or title.

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?

With no output schema, the description partially compensates by sketching the return payload ('identity + headline figures') and fixing units. It does not mention default sort (total_assets) or result-size behavior, but those live in the schema, so the remaining gap is small for a seven-parameter read-only list tool.

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 description coverage is 100%, so every parameter is already documented with examples, enums-by-text, and units. The description's unit note echoes what the schema already says for min_assets ('$000s') and adds no syntax, default, or interaction detail (e.g., how q behaves when combined with sort/pagination) beyond it. Baseline 3 applies.

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?

The description states a specific resource and scope: a directory of all FDIC-insured banks carrying identity plus headline figures. An agent can tell it is a bulk/list endpoint rather than a single-entity lookup, though it never names the sibling 'bank' or 'bank_profile' tools it overlaps with, so differentiation is left implicit.

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?

Usage is only implied: the word 'Directory' plus the optional q/state/tier filters suggests browse-and-filter scenarios. There is no explicit statement of when to prefer this over bank_search_index, bank_compare, or bank_deep_dive, and no exclusions or prerequisites are given.

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.

Resources