Skip to main content
Glama

Peer Percentile Ranks

ranks
Read-only

Pre-computed percentile rank within the bank's asset-size cohort. (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": "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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by saying the rank is 'pre-computed' and 'derived' from BankRegReports, indicating it is a stored lookup rather than a live calculation, but it says nothing about missing-metric behavior, default metric, or what the response contains.

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 brief sentences with the core purpose front-loaded and zero padding. The parenthetical source attribution is marginal but cheap, and under-specification rather than verbosity is the real issue.

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?

A simple three-parameter read tool with a fully documented schema and no output schema, so much is already covered. Still, the agent is not told what the returned percentile structure looks like or what happens when a metric has no peer data, leaving a small but real 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 metric, rssd_id, and report_date are all documented in the schema, including the 'latest' default for report_date and the pointer to the `metrics` tool. The description adds nothing on top of that, so the baseline 3 applies; 'asset-size cohort' hints that cohort is implied rather than an input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (a pre-computed percentile rank) and its scoping basis (the bank's asset-size cohort), so the agent grasps the concept. But it is a noun phrase with no verb, and it never distinguishes itself from the many peer/rank siblings (bank_ranks, bank_peer_ranking, peer_comparison), which is exactly where confusion arises.

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 statement of when to use this tool, no prerequisites, and no named alternative among the sibling ranking/comparison tools. The agent must infer from the fragmented name and the cohort phrase which of the several peer tools fits.

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