Skip to main content
Glama

Holding Company Snapshot

holding_company
Read-onlyIdempotent

Latest snapshot 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"
  }
}

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?

The annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new context that annotations cannot express: the upstream dataset (Fed FR Y-9C), dollar figures in $000s, and ratios expressed as percentages — units are exactly what agents get wrong. It stops short of saying what happens when the RSSD id is unknown or whether 'latest' is tied to a specific report quarter.

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: the first states what the tool returns, the second states units/source. Nothing is padded and the identifying information is front-loaded.

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 one-parameter, read-only lookup with full annotation coverage, this definition supplies the recency ('latest'), the source dataset, and unit conventions — the main things an agent needs to interpret results without an output schema. The remaining gap is that it does not enumerate what the snapshot contains beyond 'dollar amounts and ratios', nor note whether non-holding-company ids return an error or empty result.

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% with a single required rssd_id that is already documented, so the schema carries parameter semantics. The description adds the narrower point that the id must resolve to a bank holding company (not a commercial bank or credit union), which is useful but not syntax-level detail. Baseline 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?

It names the specific resource (one bank holding company) and the specific shape of the result (a latest snapshot), which implicitly separates it from list-style siblings such as holding_companies and from the time-series sibling holding_company_trends. It does not name any sibling outright, so differentiation is implied rather than stated.

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 word 'one' signals that the tool takes a single institution, which hints at when it applies versus a multi-company listing. However, there is no explicit when/when-not guidance, no pointer to holding_companies or holding_company_trends, and no note about needing an RSSD id obtained elsewhere.

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