Skip to main content
Glama

Bank Branches, FDIC

bank_branches_fdic
Read-onlyIdempotent

FDIC institutional branch registry with service-type codes and CBSA designation. (Source: FDIC Institution Directory.)

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_branches_fdic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 1000, max 5000).
stateNoTwo-letter state filter.
offsetNoPagination offset.
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds the authoritative source and mentions returned content such as service-type codes and CBSA designation, but it does not explain filtering, pagination, permissions, or result shape beyond that.

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?

The definition is very short and front-loads the dataset identity and key content attributes. The parenthetical source citation is useful, though it repeats 'FDIC' and the description remains label-like rather than task-oriented.

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

Completeness2/5

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

For a tool requiring rssd_id and supporting state, limit, and offset, the description never explains that it returns branches for a specific institution or how pagination and filtering work. With no output schema, the description leaves too much for the agent to infer.

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 parameters are already documented. The description adds no parameter-level meaning, such as explaining that rssd_id is the required institution identifier or how state, limit, and offset behave.

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?

The description clearly identifies the FDIC institutional branch registry and names content attributes such as service-type codes and CBSA designation. It does not state an explicit operation or distinguish this tool from siblings like bank_branches_counties or bank_branches_nic, so it falls short of a 5.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. An agent must infer from the tool name that this is an FDIC branch query tool and guess how it differs from the other branch tools.

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