Skip to main content
Glama

Bank Branch Rollup

bank_branches_rollup
Read-onlyIdempotent

Per-year branch count and total deposits rollup. (Source: FDIC SoD.) 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_rollup"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior context the annotations do not: the unit convention ($000s) and that ratios are percentages, plus the FDIC SoD provenance. It stops short of saying what the per-year granularity actually spans or whether all years are returned.

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 short sentences, zero filler, with the output content front-loaded and the unit convention immediately after. Every clause carries information an agent would otherwise have to guess.

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 single-parameter, read-only rollup with no output schema, the description covers what is returned, the unit scale, and the data source. The only real gap is the time coverage of 'per-year' and whether multiple years come back in one call, which matters for a tool with no output schema.

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?

Only one parameter, rssd_id, and schema description coverage is 100%, so the schema already explains it as the Federal Reserve RSSD id. The description adds nothing about the identifier but nothing is missing either; baseline 3 applies when the schema fully carries the parameter.

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?

States a concrete output shape: per-year branch count plus total deposits, sourced from FDIC SoD. An agent knows exactly what data comes back. It does not, however, distinguish itself from close siblings like branches, bank_branches_fdic, or deposits_trends, which the description never mentions.

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?

No when-to-use guidance at all: no mention of when this rollup is preferable to branches or deposits_trends, no prerequisites, no exclusions. The agent must infer selection purely from the phrase '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