Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

13F Portfolio Overlap

thirteenf_overlap
Read-onlyIdempotent

Compute portfolio overlap between two 13F managers from their FULL holdings (postgres-backed — no top-50 cap, so small-tail overlaps are included). Returns the shared CUSIPs with each manager's position (shares, value_dollars), plus overlap statistics: shared count, shared value, and overlap percent on each side (shared_value / manager's total_value). Useful for 'do BRK and Bridgewater agree on anything?' or 'how much do two activists overlap'. Common-stock-long convention (share_type='SH', put_call IS NULL). Data mirrors EDGAR 13F on a ~4h cycle; report_date defaults to the latest mature quarter. manager_a / manager_b each carry accession + filing_url (that manager's 13F for the quarter; open with get_filing) and accessions (every 13F/amendment behind it).

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_a": "<cik_a>",
      "cik_b": "<cik_b>"
    },
    "name": "thirteenf_overlap"
  }
}

Input Schema

NameRequiredDescriptionDefault
cik_aYesFirst manager CIK (e.g. 1067983 = Berkshire Hathaway).
cik_bYesSecond manager CIK to compare against.
report_dateNoPoint-in-time quarter (YYYY-MM-DD). Default: latest. When historical, routes to postgres current_holdings_mat and computes overlap from full holdings (not top-50 cap). Echoes as_of_effective.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/no-destruction, and the description goes well past them: it discloses the postgres backing without a top-50 cap, the common-stock-long convention (share_type='SH', put_call IS NULL), the ~4h EDGAR mirror cycle, the default 'latest mature quarter,' and per-manager accession/filing_url metadata for follow-up. That is exactly the operational context an agent needs before calling.

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 the core purpose and scope, then layered detail; nearly every clause carries information. It is dense to the point of being a single long paragraph, and the accession/filing_url sentence could be tightened, but there is no filler.

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 still enumerates the returned fields (shared CUSIPs, shares, value_dollars, shared count/value, per-side overlap percent and its formula) and names the convention and freshness model. For a 3-parameter read tool this leaves no material gap.

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% and already documents cik_a (with the Berkshire example) and report_date's historical routing and as_of_effective echo, so the description mostly restates that. The one genuine addition is the reminder that report_date defaults to the latest mature quarter, which is marginal over the schema.

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?

States a specific verb and resource: 'Compute portfolio overlap between two 13F managers from their FULL holdings.' The addition of 'FULL holdings (postgres-backed — no top-50 cap)' distinguishes it from the single-manager portfolio siblings, so an agent can pick it without opening the schema.

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?

Gives concrete invocation scenarios ('do BRK and Bridgewater agree on anything?', 'how much do two activists overlap'), which clearly frames it as a pairwise comparison tool. It stops short of naming exclusions or alternatives (e.g. consensus/holders tools) for when a pairwise overlap is the wrong choice.

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