Skip to main content
Glama
jflamb

FDIC BankFind MCP Server

by jflamb

Get Failure Details by Certificate Number

fdic_get_institution_failure
Read-onlyIdempotent

Retrieve failure details for FDIC-insured institutions using their certificate number to access specific failure records and structured data.

Instructions

Retrieve failure details for a specific institution by FDIC Certificate Number.

Use this when you know the CERT of a failed institution to get its specific failure record.

Args:

  • cert (number): FDIC Certificate Number of the failed institution

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

Returns detailed failure information 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

  • Registration and implementation of the 'fdic_get_institution_failure' tool, which queries the FDIC failures endpoint by certificate number.
      server.registerTool(
        "fdic_get_institution_failure",
        {
          title: "Get Failure Details by Certificate Number",
          description: `Retrieve failure details for a specific institution by FDIC Certificate Number.
    
    Use this when you know the CERT of a failed institution to get its specific failure record.
    
    Args:
      - cert (number): FDIC Certificate Number of the failed institution
      - fields (string, optional): Comma-separated list of fields to return
    
    Returns detailed failure information suitable for concise summaries, with structured fields available for exact values when needed.`,
          inputSchema: CertSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
          },
        },
        async ({ cert, fields }) => {
          try {
            const response = await queryEndpoint(ENDPOINTS.FAILURES, {
              filters: `CERT:${cert}`,
              fields,
              limit: 1,
            });
            const records = extractRecords(response);
            if (records.length === 0) {
              const output = {
                found: false,
                cert,
                message: `No failure record found for CERT ${cert}. The institution may not have failed, or the CERT may be incorrect.`,
              };
              return {
                content: [{ type: "text", text: output.message }],
                structuredContent: output,
              };
            }
            const output = records[0];
            const text = formatLookupResultText("Failure details", output, [
              "CERT",
              "NAME",
              "FAILDATE",
              "RESTYPE",
              "COST",
              "QBFASSET",
              "CITY",
              "STALP",
            ]);
            return {
              content: [{ type: "text", text }],
              structuredContent: output,
            };
          } catch (err) {
            return formatToolError(err);
          }
        },
      );
Behavior3/5

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

Annotations already cover key traits (read-only, non-destructive, idempotent, closed-world). The description adds useful context about return format ('detailed failure information suitable for concise summaries' and 'structured fields available for exact values'), but doesn't mention rate limits, authentication needs, or error behaviors. With annotations providing safety profile, this earns a baseline 3 for adding some behavioral context.

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 with zero waste: first states purpose, second gives usage guidelines, third describes returns. Each sentence earns its place by adding distinct value. Front-loaded with core purpose.

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?

For a read-only tool with good annotations and 100% schema coverage, the description is largely complete. It covers purpose, usage, and return characteristics. Minor gap: no output schema exists, and the description doesn't detail exact return structure or error cases, but 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 parameters are fully documented in the schema. The description briefly mentions 'fields (string, optional): Comma-separated list of fields to return' but adds no meaning beyond what the schema provides (e.g., examples of fields, formatting details). Baseline 3 is appropriate when 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 failure details') and resource ('for a specific institution by FDIC Certificate Number'), distinguishing it from siblings like fdic_search_failures (which likely searches rather than retrieves by specific identifier). The verb 'retrieve' and focus on 'specific institution' provide precise purpose.

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?

Explicitly states when to use: 'when you know the CERT of a failed institution to get its specific failure record.' This distinguishes it from search tools (e.g., fdic_search_failures) that don't require a known certificate number, providing clear alternative guidance.

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