Skip to main content
Glama

Insider Buy Signals

by com.tradestarinsider
OverviewDiscussionsAdmin

Insider cluster buys

insider_cluster_buys
Read-onlyIdempotent

Rule-2 cluster buys only (>=2 insiders buying the same issuer in-window) — the highest-signal subset. Each row carries uniform_price_cluster: true when >=3 distinct insiders bought at the IDENTICAL price on the same filed_date for the same issuer — the fingerprint of an offering/conversion (one administered price), NOT independent open-market conviction. Note Form-4 code P covers open-market purchases AND some offering/conversion purchases filed under P; the per-row offering_context flag (and uniform_price_cluster) mark the latter. Genuine clusters rank ABOVE uniform-price ones. Returns the newest 25 by default (set limit; page with offset; optional days/ticker); total_matched reports the full count. Each record carries its source filing_url.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Only rows filed within the last N days (relative to today).",
+  "type": "integer"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap.",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Rows to skip before this page (pagination). Default 0.",
+  "type": "integer"
+}
    • addedInput schema / properties / ticker
      Added value: +{
+  "description": "Case-insensitive exact ticker filter, e.g. DKS.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish the safe read-only/idempotent profile, but the description adds substantial domain behavior: the meaning of uniform_price_cluster, the caveat that Form-4 code P conflates open-market and offering/conversion purchases, the ranking rule (genuine clusters above uniform-price ones), and default ordering/pagination. This is exactly the kind of context annotations cannot carry.

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 dense and front-loads the core definition and the highest-value caveat before moving to paging details. It is longer than typical, but nearly every clause carries signal; only the parameter recap at the end is somewhat redundant with the schema.

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, the description takes on the burden of describing returns (newest 25 by default, total_matched full count, per-record filing_url) and does so. Combined with the flag semantics, an agent has everything needed to interpret results correctly.

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 four parameters are already documented, and the description largely restates limit/offset/days/ticker and the total_matched count. It adds only marginal framing (newest-first default) beyond the schema, so the baseline 3 applies.

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 precise verb+resource with an exact inclusion rule ('Rule-2 cluster buys only, >=2 insiders buying the same issuer in-window') and characterizes it as the highest-signal subset. An agent can distinguish this from the broad insider_signals_* siblings without opening any schema.

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?

The definition of what constitutes a cluster buy implies when it applies, and the warning about uniform-price clusters vs genuine conviction is useful selection guidance. However, no sibling is named and no explicit when-to-use/when-not-to-use routing is given (e.g. vs insider_signals_by_ticker or insider_filing_lookup).

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

All Insider Buy Signals toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources