Skip to main content
Glama

Bank Deposit Composition

deposits
Read-only

Deposit composition snapshot: demand, time, brokered, insured/uninsured ratios. (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"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

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 readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the upstream source (FFIEC Call Report Schedule RC-E) and the units convention ($000s for dollars, percentages for ratios), which prevents misreading outputs. It does not say which reporting period the snapshot reflects (latest quarter vs. as-of date) or how stale data may be, which is a meaningful gap for a data-retrieval tool.

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 compact sentences, front-loaded with the resource and its components, then the source and unit conventions. No filler, though the parenthetical source citation is somewhat terse and could be integrated more smoothly.

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 does the work of enumerating the returned components and the unit conventions, which is the key thing an agent needs to interpret results. The main omission is the temporal scope of the snapshot and whether the value is the most recent filing, which matters for a single-parameter data lookup.

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 coverage is 100% and the single parameter rssd_id is fully documented in the schema with an example, so the description carries little added burden. It says nothing additional about the identifier (e.g., where to obtain an RSSD id or whether non-bank entities are valid), which matches the baseline of 3 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 states a specific resource (deposit composition) and enumerates the components returned: demand, time, brokered, and insured/uninsured ratios. That is far more concrete than a tautology, but it never names or contrasts with siblings such as deposits_trends or rates_deposit, so the agent must infer that this is a point-in-time snapshot rather than a series.

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?

The word 'snapshot' hints that this is a single-period view as opposed to a time series, which implicitly routes away from deposits_trends. However, there is no explicit when-to-use statement, no exclusion of alternatives, and no guidance on when a trend or rate-focused tool would be preferable.

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