Skip to main content
Glama

BankRegReports

Bank Scorecard, Full Composite

scorecard_composite
Read-only

CAMELS category metrics with quartile letter grades, a composite grade, loan-concentration context, and ML risk tier. (Source: BRR derived (CAMELS quartile grading over FFIEC Call Report).)

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

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

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 readOnlyHint=true and openWorldHint=true, so safety and openness are covered by structured data. The description adds genuine provenance — that values are BRR-derived CAMELS quartile grading over FFIEC Call Report data — which tells the agent the data lineage and refresh source. It does not disclose coverage gaps, whether all banks have grades, or how the ML risk tier is derived, so it exceeds the annotation baseline only modestly.

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?

A single front-loaded sentence enumerates the returned components, followed by a short parenthetical source note — no filler. The nested parentheses in the source attribution ('Source: BRR derived (CAMELS quartile grading over FFIEC Call Report)') are slightly awkward but do not obscure meaning.

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 tool with no output schema, the description covers what is returned at a component level, which is the main need. However, it says nothing about the grading scale, units, or how the composite is computed, and does not differentiate this from the sibling scorecard tool — gaps an agent would notice on first call.

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 a single required rssd_id that is fully documented, so the schema carries the parameter burden. The description adds no further meaning about the identifier or its expected format. Baseline 3 is appropriate when the schema does the work.

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 names the concrete contents the tool returns: CAMELS category metrics, quartile letter grades, a composite grade, loan-concentration context, and an ML risk tier. That is much stronger than a restatement of the name. It stops short of a 5 because it never distinguishes this 'full composite' variant from the sibling 'scorecard' tool, leaving the agent to infer the difference from the name 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 what question this answers, no prerequisites, and no mention of when to prefer the plain 'scorecard', 'metrics', or 'bank_peer_ranking' siblings. The agent must infer routing from the title and name.

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