Skip to main content
Glama

Holding Company Directory

holding_companies
Read-onlyIdempotent

Directory of bank holding companies. (Source: Fed FR Y-9C.) 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": "holding_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName search, case-insensitive. Matches any part of the legal name; when that finds nothing, falls back to the site's name matcher, which forgives punctuation, spacing and common abbreviations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already supply readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context that annotations cannot: the data source (Fed FR Y-9C) and, critically, that dollar amounts are in thousands and ratios are percentages, which prevents misreading returned values. It stops short of describing result volume or pagination behavior for what could be a large directory.

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?

Two short sentences, front-loaded with identity followed by units and source. No padding or redundancy. It could be marginally better structured by folding the units note into a single clause, but nothing is wasted.

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?

For a one-parameter lookup tool with a fully described schema and a clear annotation set, the definition covers identity, source and units. What is missing is the routing information an agent needs among several similarly named siblings (directory vs single company vs trends), which is the main open question for correct tool selection.

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 coverage is 100% and the single q parameter already documents case-insensitivity and the fuzzy fallback matcher in detail. The description adds nothing beyond that, so the baseline 3 for a fully documented schema is appropriate; there is no gap for the description to compensate for.

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

Purpose3/5

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

"Directory of bank holding companies" identifies the resource and implies a listing operation, but there is no explicit verb and no differentiation from the sibling tools "holding_company" (singular detail) or "holding_company_trends". An agent knows roughly what data domain it touches but must guess whether this returns one record or many.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use guidance, no exclusions, and never names an alternative such as holding_company or holding_company_trends. The only hint is that q is optional, implying an unfiltered full-listing mode, which the agent must infer.

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