Skip to main content
Glama

Insider Buy Signals

by com.tradestarinsider
OverviewDiscussionsAdmin

Recent activist stakes (SEC Schedule 13D)

activist_stakes_recent
Read-onlyIdempotent

Recent activist Schedule 13D / 13D-A filings on US-listed companies, newest first then by stated-intent strength (control/take-private > board/proxy > strategic/value, or none stated). Returns the newest 25 by default (set limit; page with offset); total_matched reports the full count. Optional min_percent (percent-of-class floor), ticker, and days (last-N-days window). Every stake carries its source filing_url; filings without a source link are dropped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOnly stakes filed within the last N days.
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.
tickerNoFilter to one subject ticker (case-insensitive), e.g. DH
min_percentNoOnly stakes at or above this percent-of-class

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Only stakes filed within the last N days.",
+  "type": "integer"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max stakes to return (default 50)"New value: +"Max rows to return (default 25, newest first). Page with offset; the response's total_matched shows the full count. limit<=0 = no cap."
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Rows to skip before this page (pagination). Default 0.",
+  "type": "integer"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, idempotent=true, openWorld=false, so safety is covered. The description adds genuinely non-obvious behavior beyond them: default page size of 25, intent-strength sort tiebreak, total_matched reporting, and the notable data-quality rule that 'filings without a source link are dropped'.

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 is front-loaded, then sort order, then defaults/paging, then filters, then the drop rule. Every clause carries information and none is padding, though the single dense sentence spanning paging and filters is slightly overloaded for skimming.

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 still discloses the shape of the response (newest-first rows, total_matched, per-stake filing_url) and the paging contract. All five parameters are addressed and the drop rule is surfaced, so nothing needed 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.

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description reinforces rather than repeats: it restates the 25-row default, the limit/offset paging model, total_matched, and frames min_percent as a percent-of-class floor, adding light interpretive value on top of the schema.

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?

States a specific resource and scope: 'Recent activist Schedule 13D / 13D-A filings on US-listed companies', with a defined sort order. An agent immediately knows this is a recency list of activist filings, but the description never names the obvious sibling verify_activist_13d, so the boundary between 'list recent' and 'verify a specific filing' is left to inference.

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 'Recent ... filings' plus the optional filters (min_percent, ticker, days), which gives an agent enough to know when it applies. However there is no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as verify_activist_13d or the insider/13F siblings.

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