Skip to main content
Glama

Insider Buy Signals

by com.tradestarinsider
OverviewDiscussionsAdmin

Today's insider-buy signals

insider_signals_today
Read-onlyIdempotent

Rule-2 insider-buy signals filed today (SEC code P purchases). Code P is not necessarily open-market: each record carries offering_context (true = an IPO/offering/private-placement allocation, NOT an open-market buy). Returns the newest 25 by default (set limit; page with offset); the response's total_matched reports the full count. Optional days/ticker filters. 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.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real substance beyond them: the caveat that code P is not necessarily open-market and that offering_context=true means an allocation rather than a buy. It also discloses the default page size and the total_matched count, which is exactly the kind of data-quality/pagination context an agent needs.

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 core identity (rule-2 code P purchases today) before moving to caveats and pagination. Dense but each clause carries information; slightly long for a single block of prose.

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?

With no output schema, the description helpfully names key response fields (offering_context, total_matched, filing_url) and the pagination contract, so an agent can interpret results. It stops short of describing the full record shape, but nothing essential to correct invocation 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 description coverage is 100%, so days, limit, offset, and ticker are fully documented in the schema already; the description largely restates limit/offset behavior and the default of 25. Baseline 3 is appropriate because the schema carries the parameter meaning.

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+resource+scope: 'Rule-2 insider-buy signals filed today (SEC code P purchases)'. The 'filed today' scoping plus the code-P detail distinguishes it from insider_signals_by_date_range and insider_signals_by_ticker without opening 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 Guidelines3/5

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

It explains how to call it (default 25, page with offset/limit, optional days/ticker filters) but never explicitly says when to prefer this over the sibling date-range or ticker variants, nor any when-not conditions. Usage is implied rather than stated.

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