Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Adviser Profile (Form ADV: RAUM, disciplinary, custody flags — 13F manager quality)

adv_manager_profile
Read-onlyIdempotent

Form ADV manager identity card — for a 13F filer (by ticker, CIK, or CRD), return SEC-registered adviser metadata: legal firm_name, registration_type (SEC / ERA / STATE), current RAUM (regulatory assets under management) + as-of date + account count, private-fund footprint (n_private_funds, total gross asset value, top fund type), disciplinary history (has_serious_disciplinary + DRP counts), and custody red-flag indicators (self_custody, related_person_custody, auditor_pcaob_registered, n_redflags).

The 13F lift: 13F shows you positions; ADV shows you whether the manager behind them is a credible $20B clean shop or a $200M outfit with a disciplinary record. Use to filter '13F new position from manager X' for actual quality.

Key semantics (worth surfacing to the LLM):

  • The 13F-join key is cik. 5,501 of 52,228 advisers have cik resolved — RIA-only advisers (don't manage qualifying institutional accounts) have cik=null; those don't file 13F anyway, so the null is consistent.

  • Counts and flags are point-in-time off the adviser's LATEST ADV filing. RAUM history is in adv_manager_raum_trend.

  • has_serious_disciplinary (as of 2026-06-13) covers criminal + civil + registered-IA regulatory DRPs — firm-level serious doubled 291 → 1,261 when regulatory landed. Pre-2025 dormant/deregistered firms' regulatory is phase-2 (still backfilling), so this metric still undercounts on inactive advisers. For the queryable detail (regulator, sanction, date, monetary amount, allegations) call adv_manager_disciplinary_detail.

  • n_redflags (range 0-N, max-1-or-2 in practice) is a rare weak-auditor signal — 387 firms have ≥1. Combine with auditor_pcaob_registered=false for the strongest red-flag screen.

  • total_gav (gross asset value of private funds) is denominated in USD; current_raum is the regulatory metric. They can diverge — RAUM is the headline number 13F LPs care about.

Compact fee block (2026-06-11, when present): each adviser carries a fees block from their latest brochure. Live coverage 23,266 advisers / 2,236 13F-joinable. fees.fee_data_available=false is the explicit empty signal — never treat as 'no fees.' Critical NULL semantics: when headline_perf_fee_pct IS NULL, read defers_to_governing_docs FIRST. true → 'performance fee exists, rate is in the LPA/PPM' (91% of private-fund advisers do this). Only false+NULL supports 'no performance fee disclosed.' For component-level detail + raw_excerpt + confidence, call adv_manager_fees.

Each adviser row carries source_filing_id (the Form ADV filing the profile is read from) and its fees block carries source_filing_id + source_brochure_id (the brochure the fee data was extracted from; if_adv_brochure opens it).

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

Input Schema

NameRequiredDescriptionDefault
crdNoAdviser CRD (Central Registration Depository) ID — the primary key. Use when the adviser has no SEC CIK (RIA-only), or when you already know the CRD from `adv_screen_managers`.
as_ofNoPoint-in-time date (YYYY-MM-DD). When set, returns the latest ADV filing dated at or before this date, from `manager_profile_history` (300K rows, 23K firms, 2017-10 → 2026-05). Defaults to current latest snapshot. ERA/STATE-only firms (no date_submitted) fall back to current snapshot. Echoes `as_of_effective` = the actual raum_as_of of the returned row.
ticker_or_cikNoTicker (e.g. 'BRK-A') or SEC CIK integer. Resolved via Atlas to CIK then to adviser. For RIA-only advisers (no CIK), pass `crd` directly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds substantial context beyond them: point-in-time snapshot semantics, the cik=null meaning for RIA-only advisers, a documented undercount caveat on has_serious_disciplinary for inactive firms, and explicit NULL handling for the fees block (defers_to_governing_docs must be read first). The remaining gap is that it never frames these as data-freshness/latency caveats for the whole row.

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 is front-loaded and the bolded section headers aid scanning, but the text runs ~450 words with meta-commentary aimed at a prompt author rather than an agent ('worth surfacing to the LLM', 'Critical NULL semantics') and restates field-level detail at length. Several sentences could be compressed without losing caller-relevant facts.

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, the description carries full responsibility for describing return values, and it does so field by field, including units (total_gav in USD vs current_raum), ranges (n_redflags 0-N), and provenance fields (source_filing_id, source_brochure_id). An agent can call this and interpret the result without opening the schema.

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 decision value: it explains that cik is the 13F join key and that cik=null is a consistent state for RIA-only advisers, which tells the agent to fall back to crd. The as_of and ticker_or_cik behavior is already fully specified in the schema, so no further credit there.

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 gives a specific verb (return), resource (Form ADV adviser metadata), and an enumerated field set (firm_name, registration_type, RAUM, private-fund footprint, disciplinary flags, custody flags). It also explicitly distinguishes itself from three named siblings that own the detail-level views.

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?

The '13F lift' paragraph states the concrete use case (screening a 13F new position for manager quality), and the description routes to adv_manager_disciplinary_detail, adv_manager_raum_trend, and adv_manager_fees for deeper queries. It never states a when-not-to-use condition or prerequisites, so it falls short of a 5.

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