Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

13F Manager Portfolio

thirteenf_portfolio
Read-onlyIdempotent

Get the full portfolio for a 13F manager (hedge fund, asset manager, pension, etc.), postgres-backed. Returns the manager's positions (rank, ticker/cusip, shares, value_usd, qoq_action) — the exhaustive book, not a top-50 cap — plus portfolio aggregates and the v3 accumulation signals. Lookup by CIK (preferred) or filer_name (case-insensitive exact match). For Berkshire Hathaway use cik=1067983.

limit caps the returned position rows (default 50); the response reports the true full count. For a manager+security multi-quarter trail use thirteenf_position_history. Data mirrors EDGAR 13F on a ~4h cycle; report_date defaults to the latest mature quarter. The header carries accession + filing_url (the manager's 13F for the quarter; open with get_filing) and accessions (every 13F/amendment behind the quarter).

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

Input Schema

NameRequiredDescriptionDefault
cikNoManager CIK (preferred — direct lookup). Example: 1067983 = Berkshire Hathaway.
limitNoNumber of top positions to return (default: 50, max: 50)
filer_nameNoExact manager name (case-sensitive). Use only if CIK unknown. Example: 'Berkshire Hathaway Inc'.
report_dateNoPoint-in-time quarter (YYYY-MM-DD). Default: latest. When historical, routes to the postgres-backed thirteenf_portfolio_full (which reads current_holdings_mat keyed by (cik, report_date) — the PIT-correct backend smart_money 2026-06-12 pointed at). Echoes as_of_effective. CAVEAT: reflects current amendment state; late RESTATEMENT amendments can change historical answers (rare, ~3.4K total in corpus, mostly old).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/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 materially beyond them: the ~4h EDGAR mirror cycle, the fact that limit truncates rows while the response reports the true full count, that report_date defaults to the latest mature quarter, and that late RESTATEMENT amendments can retroactively alter historical answers. It also explains what the header carries (accession, filing_url, accessions) and points to get_filing to open the filing.

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?

Front-loaded with purpose and return shape, then lookup key, then limit semantics, then sibling routing and freshness caveats — a sensible order. The report_date discussion in the description leans on backend internals (current_holdings_mat, 'smart_money 2026-06-12 pointed at') that don't help an agent decide or call, costing some tightness.

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 four-param, optional-only read tool with no output schema, the description covers what comes back, how truncation works, defaults, freshness, lineage fields, and the alternative for a related question. Nothing an agent needs in order to call it correctly is missing, aside from the case-sensitivity discrepancy noted above.

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 baseline is 3; the description still adds meaning by explaining that limit caps returned position rows while the true count is reported, and that historical report_date routes to the postgres-backed thirteenf_portfolio_full and echoes as_of_effective. However, it states filer_name is 'case-insensitive exact match' while the schema says 'Exact manager name (case-sensitive)' — a direct conflict that could cause a failed lookup.

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?

Opens with a specific verb and resource ('Get the full portfolio for a 13F manager'), names the returned fields (rank, ticker/cusip, shares, value_usd, qoq_action), and explicitly contrasts scope with a top-50 cap. It also names the sibling to use for a different question, so an agent can route 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?

States lookup precedence ('CIK (preferred) or filer_name'), gives a concrete worked example ('For Berkshire Hathaway use cik=1067983'), and explicitly redirects the multi-quarter manager+security trail case to thirteenf_position_history. When-to-use and when-to-use-something-else are both present.

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