Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Corp Bond Holders (which funds + crowding stats, by CUSIP)

tranche_bond_holders
Read-onlyIdempotent

Funds holding a corporate bond by CUSIP, as-of a date, with crowding stats. Returns: ranked list of holding funds (series_id, series_name, registrant_cik, par, value_usd, implied_price) AND a concentration block (n_holders, total fund-held value, top-5 share of total). Source: N-PORT-P fund-holdings panel.

IMPORTANT: 'fund-held' means SEC-registered funds (mutual funds + ETFs) only. Insurers / pensions / foreign holders are NOT in this panel — so this is the fund slice of the ownership picture, not the full holder list. Use as a large point-in-time, identifier-exact sample. Historical depth: 2019-09-30 to current.

Identifiers: series_id (S000…) is the fund; registrant_cik is the fund family (one registrant has many series — don't confuse these). Each holder row carries accession + filing_url (the fund's N-PORT for that report date; open with get_filing).

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": {
      "cusip": "<cusip>"
    },
    "name": "tranche_bond_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReport date YYYY-MM-DD (default: latest from pipeline_meta).
cusipYes9-character CUSIP for the bond.
top_nNoMaximum holders to return (default 50, max 500). Crowding stats are always computed over ALL holders, not just the returned page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description layers on real behavioral context: data source (N-PORT-P), historical depth (2019-09-30 to current), the panel's structural coverage gap, and a cross-reference that each holder row carries accession + filing_url openable via get_filing. This is exactly the kind of disclosure annotations cannot provide.

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?

Front-loaded with the core operation, then a Returns block, then labeled caveats (IMPORTANT, Identifiers) that make it skimmable. Slightly dense with field enumerations, but each label maps to a real decision an agent has to make.

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?

There is no output schema, so the description carries the return-value burden and does it well: ranked holder rows with named fields plus a concentration block. The remaining gap is mechanical rather than semantic — nothing on result size, latency, or what happens when a CUSIP has zero holders in the panel.

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 the baseline would be 3; the description earns more by disambiguating series_id (the fund) from registrant_cik (the fund family, many series) — a distinction the schema does not make. It does not add further detail on as_of format or the top_n page-vs-population split beyond what the schema already states.

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?

Names a specific verb and resource ('Funds holding a corporate bond by CUSIP, as-of a date, with crowding stats') and immediately bounds the universe: SEC-registered funds only, excluding insurers/pensions/foreign holders. That scoping is what separates it from the broader holder tools like holders_combined or thirteenf_holders without needing to name them.

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 explicit situational guidance ('Use as a large point-in-time, identifier-exact sample') plus a clear when-NOT signal by declaring the panel excludes insurers, pensions and foreign holders. It stops short of naming the alternative tool an agent should reach for when a full holder list is needed, so routing is left to inference.

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