Skip to main content
Glama

Bank Scorecard

scorecard
Read-only

CAMELS-style component scores (0–100) + overall letter grade. (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": "scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

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 safety is covered. The description does add one genuinely useful behavioral signal — the '(derived)' and 'Source: BankRegReports' note implies these are computed proxy scores rather than official regulatory CAMELS ratings, which matters for interpretation, but it does not spell that caveat out or say whether scores are point-in-time or trended.

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 short fragments with no wasted words, and the payload content (component scores plus letter grade) is front-loaded. The terseness borders on under-specification rather than padding, but nothing needs deleting.

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 must explain returns, and it does name the two return elements (0–100 component scores, overall letter grade). However, for a single-parameter per-bank lookup it leaves out the per-institution scope and the meaning/limitations of 'derived' scores, so it is only adequate rather than complete.

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% and the single rssd_id parameter is fully documented in the schema, so the schema carries the burden. The description adds nothing about the parameter — not even that it is required or that it returns one institution's scorecard — so the baseline 3 applies.

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 conveys what the tool returns (CAMELS-style component scores 0–100 plus an overall letter grade) but never states a verb or that it operates on a single bank identified by rssd_id. It also fails to differentiate from the sibling 'scorecard_composite', which from its name alone sounds like it may cover the same ground.

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 guidance on when to use this versus 'scorecard_composite', 'bank_profile', 'bank_compare' or any other sibling. The agent must infer that this produces a CAMELS-style rating for one institution, and nothing tells it when that is the right choice.

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