Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Adviser Private Funds (Schedule D funds + service providers)

adv_private_funds
Read-onlyIdempotent

Schedule D private funds reported by one adviser, with their service providers (auditor, prime broker, custodian, administrator, marketer). Covers both registered advisers and exempt reporting advisers (ERAs — most VC/PE funds).

This is a CURRENT-STATE register, not a per-filing time series: each fund row reflects its latest-known filing, globally, across every source that's ever reported it. A fund the adviser stopped reporting (closed/liquidated) still appears, frozen at its last reported state — there is no flag or parameter to show 'as of filing N' or to exclude closed funds; everything the adviser has ever had on file is always included.

role on each service provider is a TYPE (auditor/prime_broker/custodian/administrator/marketer), not an Item 7.B(1) sub-question number — don't present it as a literal filing-item citation.

Provider CRD/company resolution is partial (~2.4% of provider rows resolve to a company_id today) — a null provider_company_id means unresolved, not that the provider doesn't exist.

Every adviser crd in the output has the adviser's SEC cik beside it (#2287; x_crd -> x_cik, a CRD list -> ..._crd_ciks): the CIK of the 13F filer that reports under that CRD, else the CIK on its own Form ADV; ciks lists both when they differ; null when neither exists. A row that already had its own cik keeps it.

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

Input Schema

NameRequiredDescriptionDefault
crdNoAdviser CRD number.
ticker_or_cikNoTicker or CIK, resolved to the adviser's CRD via adv.manager_profile. Use `crd` directly for RIA-only advisers with no CIK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile; the description goes well beyond by disclosing that closed or liquidated funds persist frozen at last-reported state, that no as-of or exclusion parameter exists, that provider_company_id is populated for only ~2.4% of rows so null means unresolved, and that role is a type rather than an Item 7.B(1) citation. These are exactly the traps that would cause misinterpretation of a read-only result set.

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 resource definition and then layered caveats in short, scannable paragraphs; the closed-fund and provider-resolution notes are high value. The closing CRD/CIK paragraph is dense and leans toward output documentation, but it is not wasted. Minor redundancy keeps it from a 5.

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?

No output schema exists, so the description carries the return-value burden and does so substantively: it explains row grain, the service-provider list, the role field, null semantics of provider_company_id, and the crd-to-cik/x_crd-to-x_cik column mapping. Missing only explicit guidance on how results are keyed or whether providers appear on the fund row versus nested, which keeps it at 4.

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 description coverage is 100%, with both crd and ticker_or_cik already documented, including the note about using crd directly for RIA-only advisers. The description adds no parameter-level syntax or format detail; the CRD-to-CIK material concerns output columns rather than inputs. Baseline 3 applies.

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

Purpose4/5

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

States a specific resource and scope: 'Schedule D private funds reported by one adviser, with their service providers (auditor, prime broker, custodian, administrator, marketer)', plus population coverage (registered advisers and ERAs). This clearly separates it from a generic manager tool, but it never names or contrasts a sibling such as funds_managed or adv_custodians, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Useful when-not guidance is embedded ('This is a CURRENT-STATE register, not a per-filing time series... there is no flag or parameter to show as-of filing N'), which tells an agent not to reach for it for point-in-time analysis. However, there is no explicit routing to alternatives and no stated prerequisites for picking this over nearby adviser tools.

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