Skip to main content
Glama

FR Y-15 G-SIB Indicators

bank_fry15
Read-onlyIdempotent

Y-15 systemic-risk indicators for G-SIB designated banks. (Source: Fed FR Y-15.) 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_fry15"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.
report_dateNoQuarter-end date, YYYY-MM-DD. Default: latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely non-structured information: the source dataset and the units of the returned values ($000s for dollar figures, percentages for ratios), which matters because there is no output schema. It stops short of stating what happens for non-G-SIB RSSD ids.

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 compact sentences, front-loaded with the primary scope, followed by the source citation and the unit convention. Nothing is redundant and nothing is buried.

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?

With no output schema, the description must carry the return-value burden; it gives units and the source but never describes which indicator categories are returned (size, interconnectedness, substitutability, complexity, cross-jurisdictional activity) or the shape of the response, which is the main remaining gap for a single-purpose data-retrieval 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?

Schema description coverage is 100%: rssd_id is documented as a Federal Reserve RSSD id with an example, and report_date documents the YYYY-MM-DD format plus the 'latest' default. The description does not add parameter-level meaning, so the baseline of 3 applies; its unit note concerns 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?

Names a specific resource (FR Y-15 systemic-risk indicators) and a specific population (G-SIB designated banks), with the source dataset cited. It is clear what the tool returns, though it does not contrast itself with siblings such as bank_profile or bank_deep_dive, so the agent must infer that this is the specialized G-SIB dataset.

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 phrase 'for G-SIB designated banks' implicitly scopes when the tool applies, but there is no explicit when-to-use guidance, no prerequisite (e.g., that the bank must be a designated G-SIB), and no named alternative for non-G-SIB systemic-risk questions.

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