Skip to main content
Glama

Credit Quality and the Allowance

credit_quality
Read-onlyIdempotent

Past due, nonaccrual and charge-offs by loan type, the allowance rollforward and its split by loan segment, and peers, with each ratio's filed lines. (Source: FFIEC Call Report (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": "credit_quality"
  }
}

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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds genuinely useful context beyond that: the FFIEC Call Report source, the $000s unit for dollars, and that ratios are percentages with filed lines shown. It says nothing about history limits, point-in-time behavior, or response shape, so it stops short of rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste: the content inventory comes first, then units and source, which are exactly the details an agent needs to interpret the numbers. Nothing is repeated or padded.

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 only three fully documented parameters, a read-only profile and no output schema, the description covers what data comes back and in what units. What is missing is modest: no note on default peer behavior or how many quarters are returned when 'quarters' is omitted.

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 all documented in the schema itself. The description adds no further meaning about these parameters, so the baseline 3 applies.

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 specific data sets returned: past due, nonaccrual and charge-offs by loan type, the allowance rollforward and its segment split, plus peer figures. The verb is implicit (a noun-phrase inventory), but an agent can tell this is a credit-quality/allowance retrieval tool and not a generic bank profile. Sibling differentiation is only partial via the 'peers' mention.

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 choose this over siblings such as bank_trends, bank_deep_dive or peers, and no exclusions or prerequisites. The only routing hint is the word 'peers', which is a data element rather than guidance about alternatives.

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