Skip to main content
Glama

Bank Loan Portfolio

loan_portfolio
Read-onlyIdempotent

Single-bank loan composition, CRE/C&D concentration vs capital, and an asset-quality trend. (Source: FFIEC Call Report (Schedule RC-C).) 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": "loan_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.
quartersNoNumber of trend quarters (1-40, default 8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real context the annotations cannot: the upstream data source (FFIEC Call Report Schedule RC-C), that dollar values are in $000s, and that ratios are percentages — all of which prevent unit misinterpretation.

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 substantive content description, followed by compact source and unit notes. No redundant restatement of the title; the parenthetical source citation is dense rather than wasteful.

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?

For a two-parameter read tool with complete schema coverage and no output schema, the description supplies purpose, data provenance, and unit conventions, which is most of what an agent needs. It stops short of describing the shape of the returned sections (composition vs concentration vs trend) or edge cases such as missing quarters.

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 and quarters (1-40, default 8) fully documented in the schema itself. The description does not elaborate on parameter meaning beyond hinting at single-bank scoping, so the baseline of 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 a specific resource and content set: single-bank loan composition, CRE/C&D concentration versus capital, and asset-quality trend, from Call Report Schedule RC-C. An agent can tell what data comes back, but no sibling is named to disambiguate it from loan_concentration or credit_quality, which occupy adjacent 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?

The word 'Single-bank' hints that this is a per-institution view rather than a peer comparison, but there is no explicit when-to-use statement, no when-not to use it, and no pointer to an alternative such as loan_concentration. The agent has to infer routing from the phrase alone.

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