Skip to main content
Glama

Bank Peer Ranks

bank_ranks
Read-onlyIdempotent

Pre-computed percentile ranks within the bank's asset-size cohort (all metrics). (Source: BankRegReports (derived).)

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_ranks"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricNoMetric id (see the `metrics` tool for valid ids).
rssd_idYesFederal Reserve RSSD id.
report_dateNoQuarter-end date, YYYY-MM-DD. Default: latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile needs no restating. The description does add real context beyond annotations: the ranks are pre-computed/derived, come from BankRegReports, and are scoped to an asset-size cohort, which tells the agent what the numbers mean. It does not disclose whether an omitted metric yields ranks for every metric or a default, which is the main behavioral question here.

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?

One compact sentence plus a source attribution, front-loaded with the output being produced. The parenthetical '(all metrics)' is the only wording that costs clarity rather than earning 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?

With no output schema, the description should indicate what a call returns, especially whether omitting the optional 'metric' produces a vector of all metrics or a single default. The cohort scoping is covered, but the shape of the response and the metric/date defaults are left to the schema to imply.

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 description coverage is 100%, with rssd_id, report_date semantics, and default all documented in the schema, so the baseline is 3. The description contributes the cohort concept that gives the percentile values meaning, but the phrase '(all metrics)' sits ambiguously against an optional singular 'metric' parameter and does not clarify that relationship.

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 output ('pre-computed percentile ranks') and a specific framing ('within the bank's asset-size cohort'), which is far more informative than a restatement of the name. It stops short of differentiating itself from closely named siblings such as 'ranks', 'bank_peer_ranking', and 'peer_analysis', so an agent cannot tell which rank tool to pick from the description alone.

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 at all: no statement of when to prefer these pre-computed ranks over ad-hoc peer comparison tools, and no exclusions or prerequisites. Usage must be inferred from the single word 'pre-computed'.

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