Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

13F Full Holder List (exhaustive, paginated)

thirteenf_holders_full
Read-onlyIdempotent

Exhaustive, paginated list of EVERY institutional 13F holder of a ticker, from the full holdings database — with an honest total count (e.g. 'showing 1-50 of 5,610 holders'). Use this when the user wants the complete holder base, a deep tail, or a specific holder rank — NOT the top-20 snapshot (use thirteenf_holders for that, it's faster and has flow/velocity signals). Each holder: filer name, manager type/tier/notable flag, is_biotech_specialist (smart_money's tag for about 100 filers whose book is mostly biotech, rule biotech_v1), position value, shares, and qoq_action ∈ {new, exit, add, trim, unchanged} mapped from the quarter's holdings_events row, and accessions (the holder's 13F filing(s) for the quarter, newest first, including sub-CIK and amendment filings). Response also carries the v3 Layer-3 signals at the top level (consecutive_accum_qtrs, consecutive_dist_qtrs, accel_4q, avg_position_value, is_cluster_entry, is_cluster_exit, is_quiet_accumulation, corporate_action_suspect) — same names as smart_money's Qdrant snapshot payload so PIT-replay reads uniformly. Sorted by position value, largest first. Defaults to common-stock long positions as of the latest reported quarter. Coverage artifacts (#2168, 2025Q4 on): when a security joins the SEC 13(f) list (or its old CUSIP leaves as the new one joins), a holder that already owned it starts or stops reporting it; that reads reporting_started / reporting_stopped (cusip_changed when the old CUSIP left and the new one joined) with no flow, not new / exit.

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

Input Schema

NameRequiredDescriptionDefault
cusipNo9-character CUSIP (e.g. 67066G104). Either ticker or cusip required; cusip wins when both are given. Use it for lines with no ticker mapping (new share classes, retired CUSIPs such as HON 438516106). Case-insensitive.
limitNoPage size — holders to return (default: 50, max: 200).
offsetNoPagination offset for paging past the first page (default: 0).
tickerNoStock ticker symbol (e.g. AAPL, NVDA). Either ticker or cusip required.
report_dateNoQuarter-end report date (YYYY-MM-DD). Defaults to the latest reported quarter.
include_optionsNoIf true, include option (put/call) and non-common share types. Default false (common-stock long only).

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 only cover the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false); the description goes well beyond by disclosing the honest total-count reporting, sort order (position value, descending), default scope (common-stock long positions, latest reported quarter), and a genuine data caveat — the reporting_started/reporting_stopped/cusip_changed coverage artifacts that are 'not new / exit'. That last point is exactly the kind of semantic trap an agent could otherwise misread as flow.

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?

Purpose and the sibling disambiguation are front-loaded in the first two sentences, which is the right ordering. It is dense, though — heavy bold markup across long enumerations of holder fields and v3 Layer-3 signal names makes it harder to scan, and part of that enumeration reads more like output documentation than selection 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?

For a six-parameter, no-required-argument tool with no output schema, the description supplies the return shape (holder fields, top-level signal payload), sorting, default scope, and the PIT-replay naming rationale. An agent has enough to call it correctly and interpret results without guessing.

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 coverage is 100%, so all six parameters, their defaults and the cusip-wins precedence rule are already documented in structured fields. The description reinforces the pagination model ('showing 1-50 of 5,610') and the default non-option scope, but adds little parameter-level detail the schema does not already carry; baseline 3 applies.

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 ('Exhaustive, paginated list of EVERY institutional 13F holder of a ticker') and immediately scopes it against the sibling: 'NOT the top-20 snapshot (use thirteenf_holders for that)'. An agent can distinguish this from thirteenf_holders and the ranks/screen siblings 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 Guidelines5/5

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

It gives explicit selection criteria — 'when the user wants the complete holder base, a deep tail, or a specific holder rank' — and an explicit negative case with the named alternative and its tradeoff ('thirteenf_holders ... is faster and has flow/velocity signals'). Nothing about tool choice is left to inference.

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