Skip to main content
Glama

Bank FDIC History

bank_fdic_history
Read-onlyIdempotent

FDIC institutional-history change log (branch-level). (Source: FDIC.) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "bank_fdic_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 200, max 1000).
rssd_idYesFederal Reserve RSSD id.
change_codeNoFDIC structure change code filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that — source attribution and, critically, the unit conventions ($000s and percentages) needed to interpret returned values. It does not disclose ordering, pagination behavior, or how far back the history goes.

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?

Two short, front-loaded sentences with no filler — the resource identity comes first and the unit conventions follow. It is arguably slightly too terse for a history/change-log tool, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three simple parameters, one required, and no output schema, the description covers what the tool is and how to read the numbers. It omits what a change record actually contains (what a 'change_code' means, date coverage, default sort order), which an agent would want before reporting results.

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 the baseline is 3, but the description adds interpretation guidance the schema lacks: the unit conventions for dollar figures and ratios that the returned history rows will contain. One caution: the description's units note is valuable, yet the schema itself is internally inconsistent (limit says maximum 100 while its description says 'max 1000'), which the description does not resolve.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource — the FDIC institutional-history change log at branch level — and credits the source, so an agent knows what data domain this covers. There is no verb ('list'/'fetch'), so the retrieval action is only implied, and nothing distinguishes it explicitly from siblings like bank_events or filer_history.

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

Usage Guidelines2/5

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

The description contains no when-to-use guidance, no prerequisites, and no pointer to an alternative tool for related questions. The agent must infer from the name alone that this is the tool for structural change history rather than current branch data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources