Skip to main content
Glama

BRAINIAC Bank, Credit Union & Charity Registries

Look up an FDIC-insured bank

registries_fdic-bank-lookup
Read-onlyIdempotent

Find a US FDIC-insured or formerly insured institution by certificate number, RSSD id, or name in the vendored FDIC BankFind institutions file. Returns status, charter class, and end date; ambiguous names return candidates. Price $0.03 USDC. POST /api/v1/registries/fdic-bank-lookup. An unpaid call returns the x402 payment terms and does not run.

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": "registries_fdic-bank-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
certNocert, integer, from 1 to 9007199254740991. Optional.
nameNoname, string, length 2 to 200. Optional.
rssdNorssd, integer, from 1 to 9007199254740991. Optional.
limitNolimit, integer, from 1 to 50. Required.
stateNostate, string. Optional.
activeOnlyNoactiveOnly, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.
totalCandidatesNototalCandidates. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, but the description adds important details: it returns status, charter class, and end date, handles ambiguous names by returning candidates, and explains the $0.03 USDC price plus the unpaid-call behavior. Those are meaningful behavioral facts beyond the annotations, and nothing contradicts the read-only hint.

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 front-loaded with the core purpose and then adds return fields, ambiguity handling, price, endpoint, and payment behavior. It is concise overall, though the raw endpoint sentence is more operational detail than selection guidance.

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 rich schema, existing output schema, and annotations, the description supplies the extra context an agent needs: registry scope, lookup identifiers, ambiguous-name behavior, and the payment gate. Nothing essential for correct invocation appears to be missing.

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 the schema already documents all six parameters. The description still adds limited parameter meaning by mapping certificate number, RSSD id, and name to identifier-based lookup and by clarifying that ambiguous names return candidates. It leaves state, limit, and activeOnly to the 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 states a specific verb and resource: find a US FDIC-insured or formerly insured institution in the vendored FDIC BankFind file. It names the identifiers (certificate number, RSSD id, or name), which makes the tool's scope clear and distinguishes it from the NCUA credit-union and UK charity siblings.

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 gives clear context for when to use the tool: lookup by certificate number, RSSD id, or name against the FDIC institutions file. It also notes that ambiguous names return candidates. It does not explicitly state exclusions or route to an alternative, but the registry-specific scope makes the intended use obvious.

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