Skip to main content
Glama

Bank Trends

bank_trends
Read-onlyIdempotent

Quarterly time series of key metrics for one bank. (Source: FFIEC Call Report.) 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": "bank_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.
quartersNoNumber of quarters (1–100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. Beyond that, the description adds only unit conventions ($000s, percentages) and cites the FFIEC Call Report source; it says nothing about default quarter count, latency, data recency, or gaps in reporting periods, which matter for an open-world data feed.

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, front-loaded with the core purpose and followed by the unit conventions an agent needs to interpret results. No filler or repeated title text.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place to explain the returned payload, yet 'key metrics' is left entirely unenumerated and the response shape (per-quarter records, field list) is undocumented. For a time-series tool with no output schema, that is a meaningful gap, though the units note partially compensates.

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?

With schema description coverage at 100%, both rssd_id and the 1–100 quarters range are already documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about how quarters is counted (including the current quarter?) or how rssd_id maps to an institution.

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 shape: 'Quarterly time series of key metrics for one bank,' which distinguishes it from the multi-entity siblings like industry_trends or credit_union_trends by scoping to a single institution. It lacks a verb (list/retrieve) and never enumerates which metrics, so the purpose is clear but not fully sharpened against bank_profile or bank_deep_dive.

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: 'Quarterly time series' suggests trend analysis over time, and 'for one bank' implies a single-entity query. No explicit when-to-use, when-not-to-use, or named alternative (e.g., bank_profile for a point-in-time snapshot) is given, leaving the agent to infer routing.

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