Skip to main content
Glama

Regulatory Capital and Risk-Weighted Assets

regulatory_capital
Read-onlyIdempotent

CET1, Tier 1, total risk-based and leverage ratios with each one's numerator, denominator and cushion, the capital stack, risk-weighted assets by category and peers, with each line's MDRM code. (Source: FFIEC Call Report Schedule RC-R (BankRegReports).) 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>"
    },
    "name": "regulatory_capital"
  }
}

Input Schema

NameRequiredDescriptionDefault
peersNoComma-separated RSSD ids for a custom peer list.
rssd_idYesFederal Reserve RSSD id.
quartersNoQuarters of history, 1 to 20.

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, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds real context beyond that: the source schedule, the inclusion of MDRM codes on each line, and the units convention ($000s for dollars, percentages for ratios). It does not discuss history depth behavior, response shape, or limits beyond what the schema states.

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 sentences, front-loaded with the metric inventory and followed by source and units notes; little waste. The first sentence is a long comma-separated list that is dense but still scannable. The units sentence earns its place by preventing a $000s misread.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the burden of describing returns, and it does so well by naming every metric family, the capital stack, RWA breakdowns, and MDRM codes. Units and source are specified. What remains missing is usage routing and any sense of result volume, but for a single-resource read tool this is close to 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%, with rssd_id, quarters (1-20), and peers (comma-separated RSSD ids) all documented inline, so the baseline of 3 applies. The description adds no parameter-specific meaning, such as how peer comparison affects returned rows or what happens when peers is omitted. The schema does the entire job here.

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 enumerates exactly which regulatory capital metrics are returned (CET1, Tier 1, total risk-based, leverage ratios with numerator/denominator/cushion, capital stack, RWA by category and peers) and cites the underlying source (FFIEC Call Report Schedule RC-R). That specificity makes it clearly distinguishable from general risk siblings like risk_dashboard or risk_overview. It stops short of a 5 because there is no explicit verb framing and no sibling is named as a contrast.

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 guidance on when to use this tool versus alternatives such as risk_overview, risk_dashboard, bank_deep_dive, or bank_peer_ranking. Nothing states prerequisites, exclusions, or the decision rule for picking this tool. The agent must infer usage purely from the metric list.

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