Skip to main content
Glama

FDIC SDI Financials

fdic_financials
Read-onlyIdempotent

FDIC Statistics on Depository Institutions (SDI) canonical financial series for one bank - quarterly balance sheet, income, capital, asset-quality, and efficiency metrics, newest period first. (Source: FDIC SDI (Statistics on Depository Institutions).) 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": "fdic_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description nonetheless contributes real operational context not in the annotations: dollar values are in thousands, ratios are percentages, and results are ordered newest period first — all of which affect how an agent interprets and presents the output.

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?

Core capability is front-loaded in a single dense sentence, followed by the units/percent caveat that an agent genuinely needs. The parenthetical '(Source: FDIC SDI (Statistics on Depository Institutions).)' largely restates the tool name and is the one piece of near-redundant wording.

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 necessary work of specifying units, ordering, and the metric families returned. It stops short of stating how many historical periods are returned, whether any limit/truncation applies, or how an agent should obtain an RSSD id if it only has a bank name — minor gaps for a single-parameter read tool.

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?

One parameter with 100% schema coverage: the schema already documents rssd_id as a Federal Reserve RSSD id with an example. The description only reinforces that the tool is scoped to a single bank; it adds no identification, lookup, or format guidance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (retrieves) and resource (FDIC SDI quarterly financial series for one bank) plus the exact metric families covered: balance sheet, income, capital, asset quality, efficiency. An agent can immediately distinguish this from siblings like bank_fdic_history or credit_union_trends without opening either schema.

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 strongly implied by 'for one bank' and the canonical-series framing, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., when to prefer bank_compare or bank_deep_dive). The agent must infer routing from the subject matter 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