Skip to main content
Glama

Holding Company Trends

holding_company_trends
Read-onlyIdempotent

Quarterly metric time series for one bank holding company. (Source: Fed FR Y-9C.) 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": "holding_company_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

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 establish read-only, idempotent, non-destructive, open-world behavior. The description adds useful context beyond annotations: quarterly frequency, FR Y-9C source, and units for dollar amounts and ratios. It still does not describe available metrics or time range, but the key behavioral attributes are covered.

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?

The description is two compact sentences with no wasted wording. It front-loads what the tool returns, then immediately clarifies source and units.

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?

For a simple one-parameter time-series tool with full schema coverage and clear annotations, the description supplies the essential context: frequency, source, and units. It could be slightly more complete by naming the metrics or historical range, but no output schema is needed and the core invocation context is present.

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% and the sole rssd_id parameter is documented in the schema. The description reinforces that the parameter identifies one bank holding company but adds no further syntax or validation detail, so the baseline of 3 applies.

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 and output type: quarterly metric time series for one bank holding company, sourced from Fed FR Y-9C. It is clear what the tool returns, though it does not explicitly distinguish itself from sibling trend tools such as bank_trends or holding_company.

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 implied by 'for one bank holding company,' which suggests use when retrieving historical metrics for a specific holding company by RSSD id. However, it gives no explicit when-to-use guidance versus holding_company, holding_companies, or bank_trends.

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