Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

insider_flow

Read-onlyIdempotent

Per-issuer Form-4 insider-transaction rollup — the Flow signal. "Is insider activity at company X bullish or bearish over the last N days?" Separates discretionary open-market buys/sells (the signal) from planned 10b5-1 sales, option exercises, tax-withholding, and awards (noise). Backed by 11.7M Form 4/5 transaction lines (incl. derivative) from ~4.6M filings, mid-2003 to present, ~10-min fresh.

Returns: n_buyers / n_sellers / n_csuite_buyers / n_csuite_sellers, open_market_buy_usd / open_market_sell_usd / planned_sale_usd, net_discretionary_usd (open-market buys − sells; the one number the Flow formula consumes — planned sales are EXCLUDED because a pre-scheduled sale says nothing about what the insider thinks today), n_transactions, plan_flag_coverage, as_of_effective.

PIT-honest: keyed on filing_date (Form 4s land up to 2 business days after the trade, so trade-date keying is lookahead). as_of defaults to today. plan_flag_coverage=false means the window reaches before 2023-04 (when the SEC 10b5-1 checkbox became mandatory) — planned-vs-discretionary is less reliable there. Dollar figures aggregate the derived, price-sanitized value_usd (never raw filer totals, which reach $300T from price-column typos).

include_participants=true adds participants: the top insiders behind the numbers (by dollar value, up to participants_limit), each with insider_cik, name, title, side (buy / sell / planned_sale), value_usd, n_transactions, last filing date and up to 5 most recent accessions (SEC accession numbers) so every figure can be traced to a filing. For every row, call names_transactions(issuer_cik=...).

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": "insider_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoPIT cutoff YYYY-MM-DD (filing_date <= as_of). Default today.
tickerNoIssuer ticker (resolved to CIK via Atlas). One of ticker / issuer_cik required.
issuer_cikNoIssuer SEC CIK. One of ticker / issuer_cik required.
window_daysNoTrailing window in days (from as_of). Default 90.
participants_limitNoMax participants returned (default 10, max 50).
include_participantsNoAdd the top contributing insiders with CIK and accession numbers. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the read-only/idempotent annotations: discloses PIT keying on filing_date with the 2-business-day lag rationale, the pre-2023-04 plan_flag_coverage caveat, ~10-min data freshness, source scale (11.7M lines / 4.6M filings, mid-2003 onward), and why dollar figures use price-sanitized value_usd rather than raw filer totals. This is exactly the behavioral context an agent needs before trusting the numbers.

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 a one-line purpose and the motivating question, then returns, then caveats — a sensible order. It is dense and long but nearly every sentence carries non-obvious information; the heavy bolding and some parenthetical asides add visual noise without much waste.

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 present, the description fully enumerates the returned fields (n_buyers, n_sellers, c-suite counts, open_market buy/sell, planned_sale_usd, net_discretionary_usd, plan_flag_coverage, as_of_effective) plus the optional participants block. For a six-parameter aggregation tool, nothing essential to correct invocation 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 nonetheless adds meaning the schema does not — that as_of defaults to today and is a filing_date cutoff, that include_participants=true returns up to participants_limit insiders with CIK, side, value and accessions, and that planned sales are excluded from the headline number. It does not explain window_days edge behavior or ticker/CIK resolution conflicts beyond a passing mention.

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?

Opening line names a specific verb, resource and grain: 'Per-issuer Form-4 insider-transaction rollup — the Flow signal,' and follows with the exact question it answers. It also distinguishes its output metric (net_discretionary_usd) from noise categories (planned 10b5-1 sales, exercises, withholding, awards), which separates it from generic insider-history siblings.

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?

Frames the call as answering a specific analyst question ('is insider activity at X bullish or bearish over last N days') and tells the agent to follow up with names_transactions(issuer_cik=...) to trace figures to filings. It lacks explicit when-not-to-use guidance or named alternatives among the many insider_* siblings, so it stops short of a 5.

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