Skip to main content
Glama

Bank Deposit Trends

deposits_trends
Read-onlyIdempotent

Multi-quarter deposit / funding breakdown for one bank. (Source: FFIEC Call Report (Schedule RC-E).) 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": "deposits_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.
quartersNoNumber of quarters (1-80, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description adds genuinely useful context the annotations do not: the data source (Schedule RC-E), that amounts are in $000s and ratios in percent. It says nothing about coverage limits, missing quarters, or what happens with the 1-80 quarter range.

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?

Three short sentences, front-loaded with the scope and resource, then the source attribution and unit conventions. Every clause carries information; the parenthetical source citation is slightly clunky but earns its place for provenance.

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 no output schema, the description supplies the essentials an agent needs: entity scope, time dimension, units, and provenance. It stops short of indicating what measures appear in the breakdown (e.g., deposit categories) or how missing/absent quarters are handled.

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 both documented including the 1-80 bound and default of 20, so the baseline is 3. The description adds no parameter-level meaning beyond the schema; its unit notes describe outputs, not inputs.

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 scope: a multi-quarter deposit/funding breakdown for a single bank, and pins the upstream source (FFIEC Call Report, Schedule RC-E). An agent can tell it apart from a snapshot-style deposits tool by the 'multi-quarter' framing, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'multi-quarter ... for one bank' suggests trend analysis for a single institution rather than comparisons or single-period lookups. There is no explicit when-to-use versus alternatives such as deposits or bank_trends, and no stated exclusions.

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