Skip to main content
Glama

Bank Deposits by County

bank_branches_counties
Read-onlyIdempotent

Deposits, share, rank and branch count in every county the bank is in. (Source: FDIC SoD + FDIC branch directory.) 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_branches_counties"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a safe, idempotent, open-world read, so the bar is lower, and the description does add genuinely useful context: the data provenance (FDIC SoD + branch directory) and the units ($000s, percentages). It omits the as-of/reporting period for deposits and whether coverage is a single snapshot, which matters for time-series data.

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?

Two compact sentences, front-loaded with the returned fields and followed by the two details (source, units) that materially affect interpretation. No marketing filler or restatement of the title.

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 one-parameter read tool with no output schema, the description adequately enumerates the return fields and fixes the units. The remaining gap is the reporting period/vintage of the deposit figures, which an agent would need in order to interpret or compare results correctly.

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?

There is one parameter and the schema already documents it at 100% coverage ('Federal Reserve RSSD id.'). The description adds nothing about rssd_id, so this sits at the baseline where the schema does all the work.

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 the exact payload (deposits, share, rank, branch count) and the scope (every county the bank is in), which is more specific than the name alone. It does not, however, differentiate itself from near siblings such as bank_branches_fdic, bank_branches_nic, or bank_branches_rollup, so an agent still has to guess which county/branch variant to pick.

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. The only implicit signal is the per-bank county scope, which an agent must infer from the noun phrase; nothing says when this should be chosen over bank_branch_map or bank_branches_rollup.

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