Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Holder Profile (one 13F manager: style, portfolio, contacts, campaigns, position in a company)

holder_profile
Read-onlyIdempotent

One 13F manager's profile (cik; a re-registered sub-CIK reads as its canonical parent), optionally against one company. header (brand and filed name, address, phone, website, investor type, adviser CRDs); details (style, turnover band and annual turnover, market-cap focus, family equity AUM, 13F AUM, positions, activism band with 5-year campaign / fight / settlement counts, top-10 concentration, return_4q and 4Q / 2Y excess return vs the S&P 500, all as fractions); overview_text; characteristics (weighted P/E, P/B, dividend yield, average market cap); sectors (weights and change vs the prior quarter); market-cap distribution (Mega >= $200B, Large $10-200B, Mid $2-10B, Small $300M-2B, Micro); industries; top holdings, buys and sells; contacts (compliance officer, regulatory contact, 13F signer, adviser executives); people (bios); campaigns (the family's activist campaigns). With company: sector_holdings / sector_buys, position (shares, estimated average cost, unrealized as a fraction, fraction of shares outstanding, first seen, last 12 quarters split-restated) and last_vote (its funds' N-PX votes at the company's latest meeting). 13F rows (holdings, buys, sells, sector_holdings, sector_buys, position and its quarters) carry accession + filing_url (newest 13F behind the row) and accessions (every family 13F behind it). 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

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": {
      "cik": "<cik>"
    },
    "name": "holder_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesThe 13F manager's CIK, e.g. 102909 (Vanguard).
companyNoOptional ticker or CIK of a company, e.g. AAPL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add real behavioral context — and it does: sub-CIK re-registration resolves to the canonical parent, 13F rows carry accession plus filing_url and a full accessions list, quarters are split-restated, and the #2168 coverage-artifact rule explains that reporting_started/reporting_stopped/cusip_changed are not flows. That last point is a genuine interpretive trap the description defuses. Missing: nothing on response size, limits, or what happens for a manager with no 13F filings.

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?

It is front-loaded with the scope sentence, which is good, but the body is a single semicolon-chained wall enumerating dozens of fields and metric definitions. Because there is no output schema, some enumeration is justified, yet the density (nested parentheticals, 'weighted P/E, P/B, dividend yield, average market cap' style lists) makes it harder to scan than a structured or shortened form would be.

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?

With no output schema, the description must carry the return shape, and it does so comprehensively — including units ('all as fractions'), market-cap bucket boundaries, excess-return windows, and the coverage-artifact edge case. For a two-parameter read tool with full annotation coverage, little an agent needs is missing; only operational details (result size, behavior on missing filings) are absent.

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% and both parameters are documented, so the baseline would be 3. The description earns above baseline by explaining the cik normalization behavior (a re-registered sub-CIK reads as its canonical parent) and by spelling out exactly which extra sections the optional company parameter unlocks (sector_holdings, position with shares/cost/unrealized/first-seen/12-quarter restatement, last_vote). That is meaning the schema does not carry.

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?

The opening clause names a specific resource and scope: 'One 13F manager's profile (cik...), optionally against one company,' which is materially different from portfolio-listing siblings like thirteenf_portfolio or thirteenf_portfolio_full. It also enumerates the content families (header, details, contacts, campaigns, position) so an agent knows what comes back. It does not name a sibling to route away from, so it stops short of a 5.

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?

Usage is implied by the 'optionally against one company' framing, which signals that the company parameter widens the response to include position and last_vote. There is no explicit when-to-use / when-not-to-use statement and no named alternative for narrower needs (e.g. position history or proxy votes). An agent can infer the fit, but must reason about it rather than being told.

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