Skip to main content
Glama
TradestarV5

TradeStar Insider

by TradestarV5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Insider cluster buys — multiple insiders buying the same stock (SEC Form 4)

insider_cluster_buys
Read-onlyIdempotent

Find when multiple insiders buy the same company via SEC Form 4 filings; filter by ticker or days and flag uniform-price offering clusters.

Instructions

Use when the user asks about cluster buying, multiple insiders buying the same company, or the strongest insider-buying signal. Returns only clusters (>=2 insiders buying one issuer in-window), newest first; days/ticker narrow. Each row carries its source filing_url, offering_context, and uniform_price_cluster (true = >=3 insiders bought at the IDENTICAL price same day — an offering/conversion, not independent conviction). Caveat: genuine clusters rank above uniform-price ones; only purchases that pass the signal filter are returned; code P alone is not proof of an open-market buy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOnly rows filed within the last N days (relative to today).
limitNoMax rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap.
offsetNoRows to skip before this page (pagination). Default 0.
tickerNoCase-insensitive exact ticker filter, e.g. DKS.
include_unlistedNoInclude unlisted issuers (blank/NONE/N/A tickers and 5-letter mutual-fund classes). Default false = exchange-listed common stock only. Every row carries a `listed_equity` boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / include_unlisted
      Added value: +{
+  "description": "Include unlisted issuers (blank/NONE/N/A tickers and 5-letter mutual-fund classes). Default false = exchange-listed common stock only. Every row carries a `listed_equity` boolean.",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4.4/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 behavioral context well beyond them: newest-first ordering, the >=2-insider cluster definition, the meaning of uniform_price_cluster (offering/conversion, not conviction), the signal filter, and the warning that code P alone is not proof of an open-market buy.

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 the use trigger, then scope, then row payload, then caveats. Dense and semicolon-packed but every clause carries information; only the final code-P caveat is slightly tangential to invoking the tool.

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 read-only filtered-list tool with no output schema, the description covers invocation context, filter behavior, pagination hints, the shape of returned rows, and critical interpretation caveats. Nothing an agent needs to call or interpret it correctly is missing.

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 coverage is 100%, so all five parameters are already documented in the schema. The description only restates that `days`/`ticker` narrow the results, adding no syntax or format detail; the richer hints about offering_context and uniform_price_cluster describe returned fields, not parameters. Baseline 3 is appropriate.

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 (insider cluster buys on SEC Form 4) and precisely defines scope: returns ONLY clusters of >=2 insiders buying one issuer in-window. This distinguishes it from the individual-buy sibling insider_buys without needing to open either schema.

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?

Opens with explicit use triggers (cluster buying, multiple insiders buying the same company, strongest insider-buying signal) and gives an interpretive caveat that genuine clusters rank above uniform-price ones. It does not, however, explicitly name insider_buys or verify_insider_purchase as the alternative to choose for single-buyer queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools