Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

13F Cohort Flow (net buys/sells across chosen managers)

thirteenf_cohort_flow
Read-onlyIdempotent

Net 13F flow per ticker across a SPECIFIC cohort of managers for one quarter — 'what is this set of funds collectively buying or selling.' Pass the manager CIKs (resolve names with thirteenf_search_managers). Ranks by ACTUAL share-based flow (Δshares × price), so price-only moves don't show as phantom buys/sells. Returns the top securities by net flow across the cohort, with how many of the cohort's funds moved each. Use for 'what are the activists / these 8 funds accumulating.' For the market-wide 'is smart money broadly buying X' consensus, that's a different question (all-notable precompute) — this tool is cohort-scoped on purpose. Distinct from thirteenf_screen (which is cluster/velocity signals).

Cohort: EITHER cohort_ciks (explicit list, max 50) OR a NAMED cohort built from the 13F manager classification — cohort_style (e.g. activist, value, long_short, quant, macro, distressed, event_driven), cohort_tier (top_50 / top_200 / long_tail), cohort_manager_type (hedge_fund, family_office, pension, sovereign_wealth, ...), and notable_only. Named filters AND together; the cohort is capped at the 1,000 largest managers by tier (response reports cohort_size and whether it was truncated).

Per security: net_flow_usd plus how many cohort funds opened (n_new), added (n_increased), trimmed (n_decreased), fully EXITED (n_exits), or held unchanged. Exits are included in net flow by default (an exit is real selling); include_exits=false drops full exits to show only funds still holding. Coverage artifacts (#2168, 2025Q4 on): when a security joins the SEC 13(f) list (or its old CUSIP leaves as the new one joins), holders that already owned it start or stop reporting it; those new / exit rows are not trades and are left out of new-position and exit counts, flows and cluster flags. Affected rows carry coverage_artifact.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax tickers to return (default: 25, max: 100).
directionNoinflow = biggest net buys (default); outflow = biggest net sells.inflow
cohort_ciksNoManager CIKs to aggregate over (1-50). Resolve names with thirteenf_search_managers. Omit when using a named cohort.
cohort_tierNoNamed cohort: manager size tier.
report_dateNoQuarter-end (YYYY-MM-DD). Defaults to the latest reported quarter.
cohort_styleNoNamed cohort: managers whose classified styles include this one.
notable_onlyNoNamed cohort: only the ~780 notable managers.
include_exitsNoCount full exits in net flow and breadth (default true). false = funds still holding only.
cohort_manager_typeNoNamed cohort: manager type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the description correctly spends its space elsewhere: it discloses that flows are share-weighted (Δshares × price), that exits count as selling by default, that the cohort is capped at the 1,000 largest managers with truncation reported in the response, and it explains the coverage-artifact rows (#2168) that are excluded from counts. That is substantial beyond-annotation value; a small gap remains on ordering/pagination of the top-N output.

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-loads the definition and alternatives before the cohort/return-section details, and nearly every sentence carries unique information. It is long (three dense paragraphs) but structured by concern rather than padded; a slightly tighter phrasing of the cohort paragraph would earn 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?

For a 9-parameter tool with no output schema, the description still declares the return shape (net_flow_usd plus n_new / n_increased / n_decreased / n_exits / unchanged and cohort_size/truncation), the default ranking basis, and the artifact-flagging field. Nothing an agent needs to call this correctly is missing.

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 the baseline is 3; the description exceeds it by explaining that `cohort_ciks` (max 50) and the named filters are mutually exclusive routes, that named filters AND together, and by spelling out the `include_exits=false` semantics as 'funds still holding only' with the rationale that an exit is real selling. That is meaning, not restatement.

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 — 'Net 13F flow per ticker across a SPECIFIC cohort of managers for one quarter' — and immediately disambiguates from thirteenf_screen (cluster/velocity signals) and the market-wide smart-money consensus precompute. An agent can pick this tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit use cases ('what are the activists / these 8 funds accumulating'), points to thirteenf_search_managers for CIK resolution, and names the alternative question (all-notable consensus) that this tool deliberately does not answer. Not just when-to-use but when-not.

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