Skip to main content
Glama

Insider Buy Signals

by com.tradestarinsider
OverviewDiscussionsAdmin

Insider-buy signals for a ticker

insider_signals_by_ticker
Read-onlyIdempotent

All Rule-2 insider-buy signals for one ticker (case-insensitive). Returns the newest 25 by default (set limit; page with offset; optional days); total_matched reports the full count. Each record carries its source filing_url. Only purchases that pass the signal filter are returned; other purchases may exist in the same filing.

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.
tickerYesTicker symbol (case-insensitive), e.g. DKS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With annotations declaring readOnlyHint, idempotentHint, and openWorldHint=false, the safety profile is covered. The description adds useful behavioral details: returns newest 25 by default, pagination behavior, total_matched count, and that only filtered purchases are included. It doesn't mention rate limits or auth, but for a read-only signal tool this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, then pagination and filtering caveats. Every clause earns its place; no repetition or filler.

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?

Given no output schema, the description explains the return shape (newest 25, total_matched, filing_url per record) and filtering behavior. It omits whether authentication or specific permissions are needed, but for a read-only public-signal tool that is a minor 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 description coverage is 100%, so the schema already documents all four parameters thoroughly. The description reiterates limit, offset, and days but adds no new syntax or format details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a precise verb (returns), resource (Rule-2 insider-buy signals), and scope (one ticker, case-insensitive). It is clearly distinguishable from siblings like insider_signals_today or insider_signals_by_date_range, which lack the ticker-specific focus.

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?

It implies usage for a single ticker and mentions pagination via limit/offset, but does not explicitly state when to prefer this over insider_cluster_buys or insider_signals_by_date_range. The context is clear but alternatives are not named.

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