Zovo Bank Insurance Check

Show a bank's FDIC history

bank_history

Read-onlyIdempotent

Use this when the user wants a bank's structure history from FDIC records: when it was established, mergers it absorbed, whether it failed or was acquired, and its successor bank. Takes one FDIC certificate number; returns the profile, status, failure details if any, institution-level events and a CSV. Branch openings and moves are not listed. Does not show financial statements.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cert": "<cert>"
    },
    "name": "bank_history"
  }
}

Input Schema

Name	Required	Description	Default
`cert`	Yes	FDIC certificate number of the bank, e.g. 3511. Find it with find_bank.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`events`	Yes
`source`	Yes
`status`	Yes
`failure`	Yes
`downloads`	Yes
`successor`	Yes
`institution`	Yes
`events_count`	No
`events_total`	Yes
`mergers_absorbed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds meaningful behavioral context beyond that: it says the tool returns profile, status, failure details, institution-level events, and a CSV, and it clarifies what is not included.

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 front-loaded with the usage condition and then efficiently states inputs, outputs, and exclusions. Every sentence contributes to tool selection or invocation.

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?

For a one-parameter read-only tool with full schema coverage, annotations, and an output schema, the description is complete: it covers purpose, input, output shape, and explicit scope limitations. Nothing material for correct invocation appears missing.

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 coverage is 100%, and the schema already documents the single cert parameter with an example and a pointer to find_bank. The description repeats that it takes one FDIC certificate number but adds no syntax or format detail beyond 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 gives a specific verb and resource: it retrieves a bank's structure history from FDIC records, including establishment, mergers, failure/acquisition status, and successor bank. It clearly distinguishes this from branch and financial-statement data, so an agent can identify the tool's scope without inspecting the schema.

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 explicitly says when to use the tool: when the user wants a bank's structure history. It also gives useful exclusions—branch openings/moves are not listed and financial statements are not shown—but it does not explicitly compare against the sibling estimate_deposit_coverage tool.

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?