fdic-banks-mcp-server

List FDIC reference vocabulary

fdic_list_reference

Read-onlyIdempotent

List the vocabulary the other fdic_ tools accept and return: every financial metric name with its FDIC field, unit, and basis (single quarter, year-to-date, or point in time), bank charter classes, failure resolution methods, the structure-change codes fdic_get_institution_history reports and the event type each maps to, insurance funds, the asset bands fdic_compare_peers uses, and the years each dataset covers. Served from built-in tables; no request to FDIC.

Input Schema

Name	Required	Description	Default
`topic`	Yes	Which table to list: metrics (names, FDIC fields, units, basis, default set), bank_classes, failure_methods, change_codes (FDIC structure-change codes with their event type and level), insurance_funds, peer_asset_bands, or coverage (years and cadence of each dataset).

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`topic`	No	The topic listed.
`entries`	No	Every entry of the topic, in table order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

changedInput schema / properties / topic / description

Previous value: -"Which table to list: metrics (names, FDIC fields, units, basis, default set), bank_classes, failure_methods, insurance_funds, peer_asset_bands, or coverage (years and cadence of each dataset)."New value: +"Which table to list: metrics (names, FDIC fields, units, basis, default set), bank_classes, failure_methods, change_codes (FDIC structure-change codes with their event type and level), insurance_funds, peer_asset_bands, or coverage (years and cadence of each dataset)."

changedInput schema / properties / topic / enum

Previous value: -[
-  "metrics",
-  "bank_classes",
-  "failure_methods",
-  "insurance_funds",
-  "peer_asset_bands",
-  "coverage"
-]New value: +[
+  "metrics",
+  "bank_classes",
+  "failure_methods",
+  "change_codes",
+  "insurance_funds",
+  "peer_asset_bands",
+  "coverage"
+]

changedOutput schema / properties / entries / items / properties / code / description

Previous value: -"The value to pass or read back: metric name, class code, method code, fund, band, or dataset."New value: +"The value to pass or read back: metric name, class code, method code, change code, fund, band, or dataset."

addedOutput schema / properties / entries / items / properties / event_type

Added value: +{
+  "description": "Event type fdic_get_institution_history gives an institution-level row with this code; every branch-level row is branch (change_codes).",
+  "enum": [
+    "merger",
+    "failure_or_assistance",
+    "branch_purchase",
+    "name_change",
+    "relocation",
+    "charter_change",
+    "opening",
+    "closing",
+    "other",
+    "branch"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / entries / items / properties / level

Added value: +{
+  "description": "Whether FDIC records the code on institution-level rows, branch-level rows, or both (change_codes).",
+  "enum": [
+    "institution",
+    "branch",
+    "both"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / topic / enum

Previous value: -[
-  "metrics",
-  "bank_classes",
-  "failure_methods",
-  "insurance_funds",
-  "peer_asset_bands",
-  "coverage"
-]New value: +[
+  "metrics",
+  "bank_classes",
+  "failure_methods",
+  "change_codes",
+  "insurance_funds",
+  "peer_asset_bands",
+  "coverage"
+]

First observedOct 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds real context beyond them: 'Served from built-in tables; no request to FDIC' tells the agent the call is offline, instant, and cannot fail on network or auth. Return content is covered by the output schema, so nothing further is required.

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?

One long but well-structured sentence that front-loads the purpose, then walks the topics in the same order as the enum, ending with the operational reassurance. Dense and informative rather than padded, though the section of the sentence duplicated by the enum description could be trimmed.

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?

With a single enum parameter, full schema coverage, an output schema, and complete annotations, the description supplies everything an agent still needs: what each topic yields, which sibling tools the tables feed, and that no FDIC request is made. Nothing material 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% and the enum is fully described, so baseline is 3; the description goes further by spelling out the payload of each topic (e.g., change_codes carry the FDIC code, its event type, and level; coverage gives years and cadence). It is slightly redundant with the schema's enum description, which limits it to a 4.

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 plus resource ('list the vocabulary') and enumerates exactly what is returned: metric names with FDIC field/unit/basis, bank charter classes, failure methods, structure-change codes, insurance funds, peer asset bands, and dataset coverage. This clearly distinguishes it from every sibling, which are data-query tools that consume this vocabulary rather than expose it.

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?

Frames the tool as the reference for 'the other fdic_ tools' and names the siblings that depend on specific tables (fdic_get_institution_history for change codes, fdic_compare_peers for asset bands), which implies calling it when you need valid field names or enum values. It stops short of an explicit 'use this before querying / do not use for financial data' statement.

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

All fdic-banks-mcp-server 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.