Skip to main content
Glama
jflamb

FDIC BankFind MCP Server

by jflamb

Get Institution by Certificate Number

fdic_get_institution
Read-onlyIdempotent

Retrieve detailed FDIC-insured bank information using its unique certificate number to access institution profiles, financial data, and regulatory details.

Instructions

Retrieve detailed information for a specific FDIC-insured institution using its FDIC Certificate Number (CERT).

Use this when you know the exact CERT number for an institution. To find a CERT number, use fdic_search_institutions first.

Args:

  • cert (number): FDIC Certificate Number (e.g., 3511 for Bank of America)

  • fields (string, optional): Comma-separated list of fields to return

Returns a detailed institution profile suitable for concise summaries, with structured fields available for exact values when needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certYesFDIC Certificate Number — the unique identifier for an institution
fieldsNoComma-separated list of fields to return

Implementation Reference

  • The handler for the fdic_get_institution tool.
      async ({ cert, fields }) => {
        try {
          const response = await queryEndpoint(ENDPOINTS.INSTITUTIONS, {
            filters: `CERT:${cert}`,
            fields,
            limit: 1,
          });
          const records = extractRecords(response);
          if (records.length === 0) {
            const output = {
              found: false,
              cert,
              message: `No institution found with CERT number ${cert}.`,
            };
            return {
              content: [{ type: "text", text: output.message }],
              structuredContent: output,
            };
          }
          const output = records[0];
          const text = formatLookupResultText("Institution details", output, [
            "CERT",
            "NAME",
            "CITY",
            "STALP",
            "ASSET",
            "DEP",
            "ACTIVE",
            "REGAGNT",
          ]);
          return {
            content: [{ type: "text", text }],
            structuredContent: output,
          };
        } catch (err) {
          return formatToolError(err);
        }
      },
    );
  • Registration of the fdic_get_institution tool with its schema.
      server.registerTool(
        "fdic_get_institution",
        {
          title: "Get Institution by Certificate Number",
          description: `Retrieve detailed information for a specific FDIC-insured institution using its FDIC Certificate Number (CERT).
    
    Use this when you know the exact CERT number for an institution. To find a CERT number, use fdic_search_institutions first.
    
    Args:
      - cert (number): FDIC Certificate Number (e.g., 3511 for Bank of America)
      - fields (string, optional): Comma-separated list of fields to return
    
    Returns a detailed institution profile suitable for concise summaries, with structured fields available for exact values when needed.`,
          inputSchema: CertSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
          },
        },
Behavior4/5

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

Annotations already cover read-only, non-destructive, and idempotent behavior, but the description adds valuable context: it specifies the return format ('detailed institution profile suitable for concise summaries') and hints at structured data availability. No contradiction with annotations, and it enhances understanding beyond the structured hints.

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 core purpose, followed by usage guidance and parameter notes in a structured format. Every sentence adds value without redundancy, making it efficient and easy to parse for an AI agent.

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?

Given the tool's moderate complexity, rich annotations, and lack of output schema, the description is mostly complete: it covers purpose, usage, and return context. However, it could slightly enhance completeness by explicitly mentioning error handling or response structure details, though annotations provide safety context.

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 the schema fully documents parameters. The description adds minimal semantics: it provides an example for 'cert' (e.g., 3511) and clarifies 'fields' as optional, but doesn't add significant meaning beyond what the schema already states. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the specific action ('Retrieve detailed information') and resource ('FDIC-insured institution'), distinguishing it from siblings like search tools by focusing on retrieval by exact identifier rather than searching. It explicitly mentions the key identifier (CERT number) and contrasts with fdic_search_institutions.

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?

It provides explicit guidance on when to use ('when you know the exact CERT number') and when not to (implying not for unknown CERTs), with a clear alternative named ('use fdic_search_institutions first'). This directly addresses sibling tool relationships and usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jflamb/fdic-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server