Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

ADV Custodians (every custodian + prime broker an adviser or 13F family names)

adv_custodians
Read-onlyIdempotent

Every custodian and prime broker an investment adviser names on Form ADV, for one adviser (crd) or a 13F filer's whole adviser family (ticker or cik, up to 60 advisers). One row per firm (names matched without legal suffixes): roles (sma_custodian = Schedule D 5.K(3), firms holding 10%+ of separately managed account assets; custodian / prime_broker = named for a private fund in Schedule D 7.B(1)), place, sma_assets_usd, n_funds and fund_gav_usd (current private funds it serves), the advisers that name it (with CRD), and since (first ADV naming it; history from 2017-10). Firms no longer named follow with former=true and until. Also returns the advisers list. Each current firm row carries source_filing_ids (the Form ADV filings behind its current rows, newest first, max 10).

adv_screen_managers filters on an adviser's main custodian only; this lists them all.

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_custodians"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoA 13F filer's CIK (its adviser family).
crdNoOne adviser's CRD, e.g. 107105.
tickerNoA 13F filer's ticker (its adviser family), e.g. BLK.
include_formerNoInclude firms the advisers no longer name (default true).

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?

Annotations already declare this a safe read (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description still adds substantial behavior beyond them: firm-name matching without legal suffixes, role semantics tied to specific ADV schedules, former firms appearing with former=true and an until date, history starting 2017-10, and a cap of 10 source_filing_ids. The CRD-to-CIK enrichment rules, including when ciks lists both and when null is returned, are behavior an agent could not infer from annotations.

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?

The most important content — what the tool returns and how it differs from the sibling — is front-loaded, and the dense field enumeration is justified for a wide row shape. Some material is over-detailed for a description, notably the issue-reference aside ('#2287; x_crd -> x_cik') and the full list of derived CIK fields, which reads like changelog rather than invocation guidance.

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?

There is no output schema, so the description carries the full burden of explaining returns, and it does: row shape, every notable field (roles, place, sma_assets_usd, n_funds, fund_gav_usd, advisers with CRD, since, source_filing_ids), plus the advisers list and former-row handling. For a four-parameter, zero-required, read-only tool this is sufficient to call it 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 description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema: it explains that ticker/cik address an entire 13F adviser family of up to 60 advisers rather than a single firm, and that include_former governs whether de-listed firms follow with former=true and until. The crd/cik/ticker interaction is described well enough to choose among them.

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 description opens with a specific verb and resource ('Every custodian and prime broker an investment adviser names on Form ADV') and immediately bounds the scope to one adviser (crd) or a 13F family (ticker/cik, up to 60 advisers). It also states row granularity ('one row per firm'), which lets an agent distinguish this from adv_screen_managers without opening either schema.

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 gives an explicit routing rule against a named sibling: 'adv_screen_managers filters on an adviser's main custodian only; this lists them all.' The crd-vs-ticker/cik choice is also clarified by the parentheticals describing each as a single adviser versus a whole adviser family. What is missing is any stated exclusion or prerequisite (e.g., what happens if no identifier is supplied, given zero required parameters).

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