Skip to main content
Glama

Bank Snapshot

bank
Read-onlyIdempotent

Latest filed-quarter snapshot for one bank: balance sheet, capital, ratios. (Source: FFIEC Call Report (Schedule RC/RI/RCR).) 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and repeatability need no restating. The description adds genuinely non-obvious context beyond them: the source report and schedules, the thousand-dollar units, and percentage formatting for ratios. It does not mention recency caveats such as reporting lag or what a missing quarter means, which would be the remaining useful detail.

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?

Three short segments with zero filler: what is returned first, then the source in parentheses, then the unit conventions. The ordering is front-loaded on the payload, with qualifying details appended rather than burying the purpose.

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 a full annotation set and a fully documented schema, the description covers the essentials: scope, source, and units. The lack of an output schema is partly offset by enumerating the returned categories, though the description never says whether the snapshot covers exactly one quarter or a short comparative window.

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 a single required parameter and schema description coverage is 100%, with rssd_id documented as a Federal Reserve RSSD id and an example value supplied. The description adds only the trivial constraint that it identifies exactly one bank, so the schema is doing the heavy lifting and the baseline of 3 applies.

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 specific verb-and-resource combination: a 'filed-quarter snapshot for one bank' with the contents enumerated (balance sheet, capital, ratios). It also names the upstream data source (FFIEC Call Report Schedule RC/RI/RCR), so an agent knows exactly what data is returned. It stops short of differentiating itself from close siblings such as bank_profile, bank_deep_dive, or bank_trends.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'latest filed-quarter snapshot for one bank' tells an agent this is a single-bank, current-period pull, which implicitly rules out trend or multi-bank comparison work. There is no explicit when-to-use statement, no named alternative for historical series, and no stated prerequisite such as knowing the RSSD id.

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