Skip to main content
Glama

Bank Peer Ranking (Live)

bank_peer_ranking
Read-onlyIdempotent

Live per-request percentile recompute across the full peer cohort. (Source: FFIEC + FDIC.) 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>",
      "metric": "<metric>"
    },
    "name": "bank_peer_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricYesMetric id to rank on (see the `metrics` tool).
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds non-annotation context: fresh per-request computation, full cohort scope, FFIEC/FDIC source, and dollar/ratio unit conventions. It does not discuss performance or failure modes, but adds enough useful behavioral context for a 4.

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 sentences are front-loaded with the purpose and then source/unit notes; there is no filler. The dense first sentence remains compact, and the unit note earns its place.

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 two-parameter read-only analytical tool, the description supplies source, freshness, cohort scope, and units. However, with no output schema it does not describe what the percentile result looks like or how the “full peer cohort” is defined, leaving a meaningful completeness gap.

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 coverage is 100%, so the schema already documents both rssd_id and metric, including the pointer to the `metrics` tool. The description adds unit conventions for results but does not add meaning to the two input parameters, so the baseline 3 is 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?

The description states a specific operation (live per-request percentile recompute) and scope (full peer cohort), and the tool name/title make clear it ranks a bank on a metric. It does not differentiate from sibling peer tools, so it is clear but not sibling-routing.

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 explicit when-to-use or when-not-to-use guidance is given, and no alternatives such as peer_comparison, peer_analysis, or bank_ranks are mentioned. “Live per-request” hints at a freshness use case but does not tell an agent when to prefer this tool over the many sibling peer tools.

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