Skip to main content
Glama

Fed Nic

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Nic Get Hierarchy

nic_get_hierarchy
Read-onlyIdempotent

Corporate ownership hierarchy for a bank or holding company, sourced from the Federal Reserve NIC (ffiec.gov/npw) Relationships data — "which holding company owns this bank?" / "list the subsidiaries of this BHC". direction="up" (default) walks the ownership chain to its top holder(s) — for a bank subsidiary this typically resolves to a single ultimate parent (e.g. a bank holding company). direction="down" lists entities OWNED BY the given RSSD ID; pass rssd_id of the TOP-TIER parent (found via direction="up") to get the full corporate family. total_subsidiary_count is a DISTINCT count computed in SQL (deduped by RSSD ID across multiple ownership paths to the same subsidiary) — it is always the true total, independent of limit/offset; use offset to page beyond the first limit rows. Coverage note: this is our own computed closure over NIC's public Relationships file, not necessarily identical to NIC's own web UI tiering figure — see pack README.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoFor direction="down": max subsidiary rows to return, 1-200, default 50 (total_subsidiary_count is always the true distinct total, not the page size)
offsetNoFor direction="down": pagination offset into total_subsidiary_count, default 0
rssd_idYesNIC RSSD ID to start from
directionNo"up" (ancestors/owners, default) or "down" (subsidiaries/descendants)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With annotations already declaring read-only/idempotent, the description still adds substantial non-obvious behavior: total_subsidiary_count is a distinct SQL-computed total independent of limit/offset, offset pages beyond limit, and a coverage caveat that this is a computed closure that may differ from NIC's own UI tiering.

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?

Long but dense and front-loaded with purpose before the direction guidance. Some restatement of the total_subsidiary_count caveat and a README pointer add bulk, but nearly every sentence carries usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-shape burden, and it does so by explaining total_subsidiary_count and pagination behavior. Combined with the coverage caveat, an agent has enough to call and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it clarifies the dedup semantics of the count, that limit/offset apply only to direction="down", and that offset pages into the true distinct total. Direction semantics are reinforced with examples.

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

Purpose5/5

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

States a specific verb and resource: 'corporate ownership hierarchy for a bank or holding company' sourced from the Fed NIC Relationships data. It disambiguates the two modes up front with concrete framings ('which holding company owns this bank?' vs 'list the subsidiaries of this BHC').

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

Usage Guidelines4/5

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

Gives clear operating context: direction="up" walks to top holders, and for the down direction it instructs the caller to first find the top-tier parent via direction="up". It doesn't name sibling tools (nic_get_institution, nic_search_institutions) as alternatives, so routing between siblings is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fed Nic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources