Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

13F Position History (quarter-by-quarter trail)

thirteenf_position_history
Read-onlyIdempotent

Quarter-by-quarter history of ONE 13F manager's position in ONE security — the full entry → add/trim → exit trail, back to 2020. Use this to explain HOW a manager built or unwound a stake over time (not just the latest quarter). Returns each quarter's shares, marked value, the share count change, the actual dollar amount traded (flow_usd = Δshares × price, excludes price-only moves), and the event type (new/increase/decrease/exit/unchanged), plus a summary (first seen, latest, peak, net change). Resolve a manager name to a CIK first with thirteenf_search_managers. No other tool has multi-year position trails. 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. Each quarter row carries accession + filing_url (the manager's 13F for that quarter; open with get_filing) and accessions (every 13F/amendment 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": {
      "cik": "<cik>",
      "ticker": "<ticker>"
    },
    "name": "thirteenf_position_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesManager CIK (e.g. 1067983 = Berkshire Hathaway). Resolve names with thirteenf_search_managers.
tickerYesTicker of the held security (e.g. AAPL).

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond that: how flow_usd is computed and that it excludes price-only moves, the five event types, and the coverage-artifact semantics where a holder shows reporting_started/reporting_stopped/cusip_changed rather than a false new/exit. That last point preempts a serious misreading of the data and is exactly the kind of context annotations cannot carry.

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 use case, then return shape, then the prerequisite, with the coverage-artifact caveat last — a sensible ordering. The coverage-artifact parenthetical is dense and slightly overlong for its weight, but every clause carries operational information rather than 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?

There is no output schema, so the description carries the full burden of describing returns, and it does: per-quarter shares, marked value, share delta, flow_usd, event type, a summary block (first seen, latest, peak, net change), plus accession/filing_url/accessions. Combined with the prerequisite and caveat handling, an agent has everything needed to call and interpret this correctly.

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 both parameters are already documented, and the cik schema text already repeats the thirteenf_search_managers pointer. The description still adds value by emphasizing the strict single-manager, single-security cardinality of the query, which shapes what the agent should expect to pass. Marginal but real uplift 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 combination — quarter-by-quarter history of ONE manager's position in ONE security — and scopes it to the full entry → add/trim → exit trail back to 2020. It explicitly distinguishes itself from sibling tools ('not just the latest quarter', 'No other tool has multi-year position trails'), so an agent can route here without inspecting other schemas.

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?

Gives an explicit use case ('explain HOW a manager built or unwound a stake over time') and a concrete prerequisite workflow: resolve the manager name to a CIK via thirteenf_search_managers first. It also names the follow-on tool (get_filing) for opening the per-quarter filings, which is exactly the when-and-how guidance an agent needs.

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