Skip to main content
Glama

Bank Branches, NIC

bank_branches_nic
Read-onlyIdempotent

Federal Reserve NIC structural branches for one bank. (Source: Fed NIC.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 1000, max 5000).
offsetNoPagination offset.
rssd_idYesFederal Reserve RSSD id.
include_closedNo1 to include closed offices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is fully covered. The description contributes only the data source (Fed NIC) and the fact that these are 'structural' branches, saying nothing about paging behavior, empty results, or what include_closed actually changes.

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 sentences, source attribution parenthetical, with the scope constraint front-loaded — very little waste. The term 'structural branches' is left unexplained, which is slightly opaque for a concise framing.

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?

This is a simple single-entity read tool with full schema coverage, complete annotations, and no output schema, so the description carries a light burden and mostly meets it. The remaining gap is differentiation from the crowded set of sibling branch tools, which a single clause could fix.

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 all four parameters including rssd_id, limit, offset, and include_closed are already documented in the schema — baseline 3 applies. The description adds no extra meaning beyond that, and notably does not reconcile the schema's conflicting limit guidance (default 1000, max 5000 stated in text vs. maximum 100 in the JSON).

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 names a specific resource (Federal Reserve NIC structural branch records) scoped to a single bank, which tells an agent this returns office/branch rows rather than aggregate or county-level data. It does not explicitly compare itself to sibling tools like bank_branches_fdic or bank_branches_rollup, so the differentiator is only implied by the 'NIC' source label.

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 guidance on when to use this tool versus the other branch-related siblings, and no stated prerequisites, exclusions, or conditions (e.g. when closed offices matter). The agent must infer applicability from the tool name and description alone.

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