Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Insider Buy Track Record (graded vs S&P 500)

insider_track_record
Read-onlyIdempotent

How an insider's open-market BUYS performed afterwards against the S&P 500 (SPY), graded strong / good / mixed / weak / few. Two ways in: • a person (person_id or owner_cik) → their record plus every buy episode (date, company, role, value, price, raw and excess return at 30/90/180 days, implausible flag); • a company (ticker_or_cik) → the record of everyone who bought there, each scored on ALL their buys (any company), best records first. Per insider: grade, scored buys at 90d, hit rate (beat SPY) and median excess return at 30/90/180d, median raw 90d return, total bought, number of stocks, first/last buy, number left out.

Console's scoring of open-market buys vs the S&P 500 (SPY), price-only on unadjusted closes, calendar windows of 30/90/180 days. Buys by one insider in one stock within 30 days of the first count once, priced at the first buy. Excess = stock return − SPY return over the same window. Left out: returns above +200/300/400% (reused-ticker artifacts) and plan-buying days (8+ insiders buying the same stock on one day at an issuer with 3+ such days — employee purchase programmes). Grade (needs 3 scored buys at 90d): strong = 4+, ≥65% beat SPY, median excess ≥ +5 pts; good = ≥55%, median > 0; weak = median ≤ −5 pts and <45%; otherwise mixed. Past returns, not a prediction.

For recent buys by insiders with good records across the market, use insider_proven_buys.

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

Input Schema

NameRequiredDescriptionDefault
limitNoCompany mode: max insiders (default 50, max 200). Person mode: max episodes (default 50, max 500).
owner_cikNoThe insider's SEC CIK (Form 4 reporting owner).
person_idNomars persons_v2 UUID of the insider.
ticker_or_cikNoIssuer ticker or CIK — returns records of everyone who bought there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, non-destructive); the description adds the full scoring methodology that determines results: price-only unadjusted closes, calendar 30/90/180-day windows, dedup of buys within 30 days of the first, excess = stock − SPY, exclusions for >200/300/400% returns and plan-buying days, and the grade formula with its 3-scored-buy minimum. It also warns these are past returns, not a prediction.

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?

Purpose and the two entry modes are front-loaded as bullets, followed by methodology and the alternative-tool redirect. Dense but no wasted sentences; the methodology block is long and slightly slows scanning, keeping it from 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?

There is no output schema, so the description has to carry the return shape — and it does, listing episode fields (date, company, role, value, price, raw and excess returns at 30/90/180d, implausible flag) and per-insider aggregates (grade, scored buys, hit rate, median excess at each horizon, total bought, stock count, first/last buy, number left out). Complete for a complex scoring tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already documents all four parameters at 100% coverage, but the description adds real value: it clarifies that person_id/owner_cik switch to person mode while ticker_or_cik selects company mode, and that limit means max insiders (200 cap) in company mode but max episodes (500 cap) in person mode. That mode-dependent meaning is not obvious from the schema alone.

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: grades an insider's open-market BUYS by subsequent performance vs the S&P 500 (SPY). It explicitly separates the two retrieval modes (person vs company) and names insider_proven_buys as a different tool, so an agent can distinguish it from siblings without opening 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?

Explicitly states two ways in — person_id/owner_cik for one insider's record plus episodes, ticker_or_cik for everyone who bought a given company — and directly routes a related use case (recent buys by good-record insiders across the market) to insider_proven_buys. Nothing about selection is left 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