Skip to main content
Glama

Bank Profile Composite

bank_profile
Read-onlyIdempotent

Above-the-fold composite: snapshot + scorecard + ranks + events + ML prediction. (Source: BRR composite (FFIEC + ML + NIC).) 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_profile"
  }
}

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 readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: dollar amounts are in $000s, ratios are percentages, and the data provenance is BRR composite (FFIEC + ML + NIC). It does not mention data vintage/freshness or response size, which matters for a composite that aggregates five data domains.

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 compact sentences with the component list front-loaded, and the units caveat placed where it will actually be read before interpreting numbers. The parenthetical provenance acronym stack (BRR/FFIEC/ML/NIC) is dense jargon but short and does not bloat the definition.

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

Completeness3/5

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

For a one-parameter read-only composite with no output schema, the description covers what domains are returned and how to read the units, which is reasonably complete. It stops short of describing freshness, coverage, or what a missing/gap-filled value looks like — meaningful gaps for an aggregated multi-source profile.

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) at 100% schema description coverage, so the schema already documents it fully. The description adds no extra meaning about the identifier beyond what the schema states, making the baseline 3 appropriate.

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 that this is a composite and enumerates exactly what it bundles (snapshot + scorecard + ranks + events + ML prediction), which lets an agent distinguish it from the individual sibling tools like scorecard, ranks, events, and prediction. The verb is implicit (a profile getter), so it falls short of a fully explicit action statement.

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?

"Above-the-fold" implies a first-look overview and the component list implies 'use this instead of calling the five siblings separately,' but neither is stated as an explicit rule. There is no when-not guidance pointing to bank_deep_dive, bank_trends, or the component tools for drill-down.

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