Skip to main content
Glama

BankRegReports

Failures by Year

failures_by_year
Read-only

Bank failure counts and total assets by year. (Source: FDIC.) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "failures_by_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFilter to one year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine context the annotations don't: the data source (FDIC), that dollar figures are in thousands, and that ratios are percentages — all of which prevent misreading returned values.

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 short sentences, front-loaded with the purpose and followed by the unit conventions that matter for interpreting output. Nothing is redundant with the tool name or schema.

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?

This is a simple one-optional-parameter read tool with no output schema, and the description covers both the metrics returned and their units. The main residual gap is the default behavior when no year filter is supplied.

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% for the single optional 'year' parameter, and the description adds nothing about parameter behavior. It does not state what happens when 'year' is omitted (presumably all years), which is the one parameter-related fact the schema cannot convey.

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 aggregation level: bank failure counts and total assets, grouped by year. That distinguishes it by shape from the sibling listing tools (failures_recent, failures_dashboard), though it never explicitly says how it differs from them.

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: an agent can infer this is the yearly time-series view rather than a recent-failures or dashboard view. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing from the name and aggregation level 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