Zovo Bank Insurance Check

Find an FDIC-insured bank

find_bank

Read-onlyIdempotent

Use this when the user asks whether a US bank is FDIC insured, or needs its FDIC certificate number, legal name, primary regulator, total assets, office count or website. Searches live FDIC BankFind records by name (optionally narrowed by state and city), by city and state, or by certificate number; returns up to 10 ranked matches and a CSV. Does not cover credit unions and does not estimate coverage (use estimate_deposit_coverage).

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": "find_bank"
  }
}

Input Schema

Name	Required	Description
`cert`	No	FDIC certificate number if known, e.g. 3511.
`city`	No	City of the bank's main office, e.g. Santa Clara. Use with state.
`name`	No	Bank name or part of it, e.g. Wells Fargo.
`state`	No	Two-letter state code to narrow the search, e.g. CA.
`include_inactive`	No	Also include closed, merged or failed institutions, e.g. true. Default false.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`note`	Yes
`query`	Yes
`ranked`	Yes
`source`	Yes
`downloads`	Yes
`institutions`	Yes
`total_matches`	Yes
`institutions_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real behavior: it queries live FDIC BankFind records, caps results at 10 ranked matches, and returns a CSV. It does not mention failure modes or rate limits, which keeps it short of a 5.

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?

Three sentences, front-loaded with the trigger condition, then the search mechanics, then the exclusions. Every clause carries information an agent needs to select and shape the call; nothing is restated from the title or schema.

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?

An output schema exists, so return values need not be spelled out, yet the description still gives the result cap and CSV format as useful context. Combined with trigger conditions, search modes, and sibling exclusions, nothing an agent needs in order to call this correctly is 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 baseline is 3, but the description adds genuine meaning by explaining how parameters combine into search modes: name optionally narrowed by state and city, city plus state alone, or certificate number. That combination logic is not visible from the flat 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?

States a specific verb and resource ('find ... FDIC-insured bank') and enumerates the data it resolves (insurance status, certificate number, legal name, regulator, assets, office count, website). It is immediately distinguishable from the siblings, which handle history and coverage estimation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with the exact user question that should route here ('whether a US bank is FDIC insured'), and adds explicit exclusions: 'Does not cover credit unions and does not estimate coverage (use estimate_deposit_coverage).' That is an explicit when/when-not plus a named alternative, which is the top bar.

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

All Zovo Bank Insurance Check tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?