Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Holders — Combined (13F + 13D/G + Form 4 insiders, one merged register)

holders_combined
Read-onlyIdempotent

One register of who holds a stock: 13F institutional holders + 13D/G beneficial-ownership stakes + Form 4 insider positions, merged into a single list sorted by holder significance (13F by value, then 13D/G, then insiders). Each row carries source so you know which filing regime it came from, and its OWN as_of — 13D/G rows are as-of the FILING date, NOT a 13F quarter-end; do not treat the three sources as the same point in time. Composes thirteenf_holders_full + search_activist_positions + insider_holdings under the hood (reuses their existing canonical-CIK rollup / dedup logic rather than re-deriving it) — call those directly if you only need one slice with its full field set (13F flow signals, 13D/G campaign/intent fields, Form 4 derivative detail all get dropped down to the common fields here).

pct_os and value_usd are null where the underlying source doesn't carry them (13D/G doesn't report a value; 13F doesn't report %-of-shares-out in this tool) — null means not reported by that source, not zero.

Form4 rows are one line per insider per vehicle: ownership is 'direct' or 'indirect: ' (e.g. 'indirect: By Limited Liability Company 1'), and value_usd is shares x the last close (value_basis says which). Emptied vehicles (0 shares) and relabeled vehicles are dropped, and so are former insiders (no Form 4 at the issuer in 548 days, insider's owner_is_current) unless include_former_insiders=true. Each drop is counted in warnings. An indirect line the owner's later filings stopped reporting is KEPT with line_status = 'last reported , absent from N later filings' and missed_later_filings = N — weigh it as possibly stale. Every row carries accession + filing_url (its source filing: the holder's 13F for the quarter, the latest 13D/G, or the latest Form 4 behind the line; open with get_filing); 13F rows also carry accessions (all 13Fs for that quarter).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "holders_combined"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows PER SOURCE (default 50, max 200) — not a combined total, so a stock with heavy 13D/G activity doesn't crowd out 13F rows.
tickerYesStock ticker.
report_dateNo13F quarter-end (YYYY-MM-DD). Default: latest mature quarter. Does not affect 13D/G or Form4, which are always current.
holder_typesNoRestrict to these sources (default: all four — 13F, 13D, 13G, Form4).
include_former_insidersNoForm4 rows: keep insiders with no Form 4 at this issuer in the last 548 days (insider's owner_is_current = false; most likely left the company; flagged likely_former_insider). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover the read-only, idempotent, non-destructive profile, and the description goes well beyond them: per-source as_of semantics (13D/G is filing-date, not quarter-end), null-means-not-reported for pct_os/value_usd, Form 4 drop rules counted in warnings, and staleness signalling via line_status/missed_later_filings. The only missing behavior is volume/size expectations, which limits it slightly below top marks.

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 merge order are front-loaded in sentence one, and the dense Form 4 caveats earn their place because there is no output schema to carry them. It is still prose-heavy with three long paragraphs of tight parenthetical clauses, which is why it falls short of a 5.

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 must carry return-value semantics, and it does: per-row source, as_of, pct_os/value_usd nullability, ownership vehicle strings, warnings counts, accession/filing_url and accessions, plus the get_filing next step. Nothing an agent needs to invoke this correctly or interpret the result is missing.

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% and the schema already documents limit being per-source, report_date not affecting 13D/G/Form4, and the include_former_insiders 548-day rule, so the baseline applies. The description reinforces these but adds essentially no new parameter-level meaning; its null and as_of notes concern output fields rather than inputs.

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 first sentence names a specific resource and verb ('One register of who holds a stock') plus its three constituent sources and the merge/sort order, and later names the siblings it composes (thirteenf_holders_full, search_activist_positions, insider_holdings). An agent can distinguish this from the single-source tools without opening any 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 states explicitly when to use the siblings instead: 'call those directly if you only need one slice with its full field set', and enumerates what is lost here (13F flow signals, 13D/G campaign/intent fields, Form 4 derivative detail). It also gives conditional guidance for include_former_insiders and holder_types, leaving little 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