Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Fund Equity Holders (which ETFs / fund series hold a stock, N-PORT fund-series grain)

fund_equity_holders
Read-onlyIdempotent

Which fund series / ETFs hold an equity ticker — from the SEC N-PORT-P fund-holdings panel, at FUND-SERIES grain (per-ETF, per-mutual-fund), amendment-resolved to each fund's latest report. Returns the ranked holder list (series_name, series_id, registrant_cik, shares, value_usd, as-of date) + breadth stats (n_funds, total shares, total fund-held value, top-5 concentration). Each holder row also carries its adviser and sub_advisers (name, CRD, CIK, role) from N-CEN; use funds_managed for every fund an adviser runs. cik beside each crd (#2287) is the adviser's SEC CIK: the CIK of the 13F filer that reports under this CRD (mars thirteenf_filer_crd_family, own_adv_crd / ncen_own_name; can be the parent's filer, e.g. Vanguard Capital Management -> The Vanguard Group 102909), else the CIK on its own Form ADV (investors_v2.adv_cik); null when neither exists (never inferred). When those two differ, ciks lists both, 13F filer first.

This is the granularity 13F cannot give. thirteenf_who_holds returns institutional MANAGERS (BlackRock, aggregated across all its funds); this returns the actual FUND SERIES (iShares Core S&P 500 ETF, Fidelity 500 Index Fund, …) with per-fund shares. Use this for 'which ETFs own X'; use 13F for 'which managers own X'.

Scope caveats (surface these): (1) SEC-registered funds only (mutual funds + ETFs) — insurers / pensions / direct holders / foreign funds are NOT in N-PORT, so this is the fund slice of ownership, not the full holder base. (2) Funds file N-PORT quarterly on staggered fiscal calendars, so 'as_of' varies per fund (each row is that fund's latest report) — it's a rolling snapshot, not a single date. (3) value_usd is the fund's marked position. Coverage: latest-quarter universe + ~3.5y history (2022-11 → current); full 6.5y backfill in progress.

Input: ticker (resolved to CUSIP internally) OR cusip (037833100-style, faster). include_preferred=false by default (common stock only; true adds preferred 'EP').

Each fund row carries fund_type from the fund's latest SEC N-CEN: etf, mutual_fund, closed_end, money_market, interval, both (one series with ETF and mutual-fund share classes, e.g. Vanguard Total Stock Market = VTI + VTSAX; share_classes then lists each class with ticker and is_etf_class), other (separate account, UIT), or null when N-CEN doesn't cover the series (e.g. liquidated before filing one). fund_type filters holders and the breadth stats — for 'which ETFs hold X' pass fund_type=['etf','both']. by_fund_type gives n_funds, value and shares per type across all holders. Each holder row carries accession + filing_url (the fund's N-PORT behind the row; open with get_filing).

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": "fund_equity_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
cusipNo9-char CUSIP (e.g. '037833100'). Faster than ticker (indexed). Provide ticker OR cusip.
limitNoMax holder rows (default 100, max 1000). Breadth stats always computed over ALL holders.
tickerNoEquity ticker (e.g. 'STRL', 'AAPL'). Resolved to CUSIP internally.
fund_typeNoOnly these fund types (any of). etf / mutual_fund / closed_end / money_market / interval; 'both' = a series with ETF and mutual-fund share classes (Vanguard VTI / VOO); 'other' = separate account, UIT etc.; 'unknown' = not in N-CEN. For 'which ETFs' pass ['etf','both']. A single string or comma list also works.
include_preferredNoInclude preferred-stock holdings (asset_cat 'EP') alongside common ('EC'). Default false = common only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description goes well beyond them: it discloses amendment resolution to each fund's latest report, the staggered quarterly fiscal calendars making as_of a rolling snapshot rather than a single date, that value_usd is a marked position, the 2022-11 to current coverage window with a backfill in progress, and that nulls are never inferred. These are exactly the caveats an agent must surface to a user.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the caveat block are front-loaded and earn their space, but the middle paragraph on CIK provenance (mars thirteenf_filer_crd_family, own_adv_crd / ncen_own_name, issue #2287, the Vanguard Capital Management example) is dense internal jargon about field derivation that an agent does not need in order to select or invoke the tool. That passage inflates the definition and dilutes the high-value routing and caveat content.

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?

For a five-parameter read tool with no output schema, the description covers the returned fields (series_name, series_id, registrant_cik, shares, value_usd, as_of, breadth stats, adviser/sub_advisers, by_fund_type, accession/filing_url), the fund_type enumeration semantics including null/unknown handling, and the scope limitations. Nothing an agent needs to call this correctly or to warn a user about coverage appears missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: ticker is resolved to CUSIP internally while cusip is indexed and faster, include_preferred=false restricts to common stock ('EC') and true adds 'EP', and limit affects only returned rows while breadth stats are always computed over all holders. The 'both' fund_type case is also explained with a concrete VTI/VTSAX example, slightly exceeding what the schema alone conveys.

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?

The opening line names a specific resource (fund series / ETFs holding an equity ticker), the data source (SEC N-PORT-P), and the grain (per-fund-series, amendment-resolved), then explicitly contrasts with 'thirteenf_who_holds' returning managers rather than fund series. An agent can distinguish this tool from every sibling without opening a schema.

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

Usage Guidelines5/5

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

It states the selection rule in both directions: "Use this for 'which ETFs own X'; use 3F for 'which managers own X'," and adds a concrete invocation recipe for the ETF case (fund_type=['etf','both']). It also routes readers to 'funds_managed' for adviser-level lookups and 'get_filing' for the underlying filing, which is explicit alternative/downstream guidance rather than implied usage.

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