Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

insider_cluster_screen

Read-onlyIdempotent

Cross-issuer discovery of insider CLUSTER BUYING — issuers where min_insiders+ distinct insiders made DISCRETIONARY open-market buys in the window. The "multiple insiders are buying their own stock" signal (the highest-conviction insider pattern). Open-market buys ONLY — option exercises, awards, and planned sales are excluded as noise. Backed by 11.7M Form 4/5 transaction lines (incl. derivative) from ~4.6M filings, ~10-min fresh.

Returns issuers ranked by distinct-buyer count then total buy value: issuer_cik, ticker, sector, n_distinct_buyers, n_csuite_buyers, open_market_buy_usd, first_buy / last_buy. PIT-honest on filing_date; as_of defaults to today. Aggregates the price-sanitized value_usd.

Each cluster carries buyers: the insiders in it (largest first, up to buyers_per_cluster) with insider_cik, name, title, value_usd and up to 5 recent accessions (SEC accession numbers), so the cluster can be traced to filings.

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

Input Schema

NameRequiredDescriptionDefault
as_ofNoPIT cutoff YYYY-MM-DD. Default today.
limitNoDefault 50, max 200.
window_daysNoTrailing window in days. Default 90.
min_insidersNoMinimum distinct buyers (default 3).
min_value_usdNoMinimum total open-market buy value. Default 0.
buyers_per_clusterNoBuyers listed per cluster, with accessions (default 10, max 50; 0 omits them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world behavior, and the description adds substantially more: data provenance (11.7M Form 4/5 lines from ~4.6M filings), ~10-minute freshness, point-in-time honesty on filing_date, price-sanitized aggregation, and the exclusion of derivative/noise transaction types. It also discloses ranking order and the nested buyers payload with accession traceability. This is context an agent could not recover from the annotations.

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?

The description is front-loaded with the core definition and signal rationale, then provenance, then return shape, which is a sensible order. It is dense and uses capitalization and bold emphasis, but every sentence carries information. Slightly long for what could be tighter prose, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 takes on responsibility for return values and does so by enumerating the issuer-level fields, the ranking rule, and the nested buyers structure with accessions. With no required parameters and full schema coverage, an agent has enough to invoke it correctly. It stops short of covering edge cases such as empty result sets or how ties beyond buyer count are broken.

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 description coverage is 100%, so every parameter is already documented, and the description adds little parameter-specific meaning beyond what the schema states. It reinforces that min_insiders counts distinct insiders and that buyers_per_cluster controls the nested buyers list with accessions, but the '0 omits them' behavior is already in the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb and scope: cross-issuer discovery of insider cluster buying, defined as issuers where min_insiders+ distinct insiders made discretionary open-market buys. It even distinguishes the signal from adjacent insider activity by explicitly excluding option exercises, awards, and planned sales. It does not name any sibling tool (insider_flow, insider_signal, insider_proven_buys), so the differentiation is conceptual rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by framing this as "the highest-conviction insider pattern" and by defining defaults (min_insiders=3, window 90 days), which suggests the intended screening scenario. There is no explicit statement of when to prefer this over a related tool, nor any when-not-to-use condition. Adequate but leaves routing to inference.

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