Skip to main content
Glama

Insider Buy Signals

by com.tradestarinsider
OverviewDiscussionsAdmin

Insider-buy signals in a date range

insider_signals_by_date_range
Read-onlyIdempotent

Rule-2 insider-buy signals filed within an inclusive ISO date range. 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
endYesInclusive end date, ISO YYYY-MM-DD
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.
startYesInclusive start date, ISO YYYY-MM-DD
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. Changed4 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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds real behavioral context beyond them: a default of 25 newest-first, offset paging, that total_matched reports the full count, and that each record carries its source filing_url. It does not mention rate limits or ordering edge cases, keeping it below a 5.

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?

Two tight sentences with the core scope front-loaded and paging details packed into a parenthetical. Every clause carries information, though the parenthetical is dense enough that a slightly cleaner split would read better.

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?

For a read-only list tool with no output schema, the description covers scope, defaults, paging, the total-count field, and a per-record field, which is enough to call and interpret it correctly. It stops short of explaining what qualifies as a 'Rule-2' signal, leaving a small domain gap.

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 the schema already documents start/end/days/ticker/limit/offset semantics; the baseline is 3. The description largely restates the same limit/offset/total_matched behavior and adds the 'inclusive' range framing, so it contributes only marginal meaning beyond the schema.

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 within an inclusive ISO date range.' The date-range framing cleanly separates it from insider_signals_by_ticker and insider_signals_today without the agent needing to open a 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 description implies when to use it (date-range browsing) and documents defaults/paging, but never explicitly names an alternative such as insider_signals_by_ticker or insider_signals_today or states the condition that picks one over the other. Usage is inferable from the sibling names 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