Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Funds Managed (every registered fund series an adviser family runs, N-CEN + N-PORT)

funds_managed
Read-onlyIdempotent

Every registered fund series (mutual funds, ETFs, closed-end funds) an adviser family runs, as adviser or sub-adviser — from SEC N-CEN adviser links joined to the N-PORT fund registry. Input a 13F manager cik (expanded to its adviser family of CRDs, e.g. State Street → SSGA Funds Management + State Street Global Advisors Ltd + …) or a single adviser crd.

Returns, per fund series: series_id, fund name, registrant (the filing trust — NOT the adviser), advisers and sub-advisers (name, CRD, CIK, role), net assets from the latest N-PORT and its date, and the N-CEN as-of date. Also per-adviser rollups (n_funds, net assets, roles) and family totals.

A CIK missing from the adviser-family table falls back to the CRD whose Form ADV carries that CIK (family_via: family_table / adv_cik_link). If no CRD is linked at all, n_funds is null (not 0) and candidate_crds lists ADV firms matching the filer name.

Notes: advisers are grouped by CRD under one canonical name (N-CEN spells some advisers several ways). Terminated adviser links are excluded. A series with no N-PORT registry row is still counted but has null net assets (n_funds_without_net_assets). Net assets are each fund's own latest N-PORT figure, so dates vary by fund. Pair with fund_equity_book(series_id) for a fund's holdings.

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 the funds list and totals; by_fund_type (family-wide and per adviser) gives n_funds and net assets per type. Each fund row carries accession + filing_url (the N-CEN filing that links the family to the fund; open with get_filing) and nport_accession + nport_filing_url (the N-PORT whose net assets the row shows; null when that filing is not on file).

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. The same cik is on the family and advisers rollups.

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

Input Schema

NameRequiredDescriptionDefault
cikNo13F manager CIK (e.g. 93751 State Street, 2012383 BlackRock). Expanded to the manager's adviser family.
crdNoA single adviser's CRD (e.g. 111242). Use instead of cik.
roleNoOnly funds where the family is the adviser, or only where it is a sub-adviser. Default any.any
limitNoMax fund rows, largest net assets first (max 2000). Totals always cover all funds.
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.

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 declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: fallback logic when a CIK is absent from the family table (family_via: family_table / adv_cik_link), n_funds being null rather than 0 with candidate_crds, exclusion of terminated adviser links, canonical-name grouping of CRDs, funds counted without net assets, and per-fund varying valuation dates. This is exactly the operational context annotations cannot carry.

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 lead paragraph is well front-loaded, but the body is dense and partly redundant with the schema — the fund_type enumeration, 'both' semantics, and the etf/mutual_fund/etc. list are restated at length in the schema already. The final paragraph on cik/ciks is verbose and could be compressed without losing meaning.

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?

With no output schema and five parameters, the description carries the full disclosure burden and does so: it enumerates returned fields (series_id, fund name, registrant, advisers with CRD/CIK/role, net assets and date, N-CEN as-of), the rollups (per-adviser and family totals, by_fund_type), filing links, and the null cases. An agent can predict the response shape and edge cases before calling.

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 is 3, but the description adds real meaning: the cik parameter is defined as the adviser's SEC CIK from the 13F filer or its own Form ADV, with ciks listing both (13F first) when they differ, and never inferred. It also clarifies that limit is largest-net-assets-first while totals always cover all funds, and explains 'both' with a concrete VTI/VTSAX example.

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 sentence names a precise verb+resource (every registered fund series an adviser family runs) and states both data sources (N-CEN adviser links joined to the N-PORT registry) plus the adviser/sub-adviser scope. It also distinguishes itself from the nearest sibling by explicitly directing holdings lookups to fund_equity_book(series_id).

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?

It tells the agent which input to supply (a 13F manager cik, expanded to the adviser family, or a single adviser crd) and pairs itself with fund_equity_book for holdings. It lacks explicit 'when not to use this' guidance against siblings such as adv_private_funds or adv_manager_profile, so it stops short of full routing clarity.

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