Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Insider Positions by Ticker

get_insider_positions_by_ticker
Read-only

Retrieve per-insider position aggregates for a stock ticker, showing which insiders hold positions plus aggregate cost and value from Form 4 filings within available coverage.

Instructions

Get per-insider position aggregates for a ticker: which insiders hold positions in the stock and their aggregate cost and value, derived from Form 4 filings. The figures are not lifetime totals: they cover only the Form 4 history Signal8 holds, which starts at the response's coverageStart date (repeated on each row), so every figure is "since coverageStart". Each row carries costBasisStatus: complete (every share the history knows was bought inside coverage), partial (the holding predates coverage, so weightedAvgCost averages only in-coverage priced buys and is not the cost of the position), or unknown (the first in-coverage event was a sale, or there was no priced buy; weightedAvgCost and costBasisTotal are null, which means not measured, not zero cost).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_insider_positions_by_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false, destructiveHint=false), so the description focuses where it should: the data coverage boundary and the meaning of `costBasisStatus` states including 'partial' not being the true cost of the position and nulls meaning not measured rather than zero. That substantially prevents misreading results. It stops short of behavioral details like rate limits, ordering, or what happens with a ticker outside coverage.

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 what the tool returns, then the caveats that matter for interpretation. The sentences are dense but each carries real content, especially the three-way `costBasisStatus` enumeration. Minor redundancy in 'not lifetime totals / only the Form 4 history Signal8 holds / since coverageStart', which restates the same limit three ways.

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?

An output schema exists, so return values needn't be explained, and the description instead covers the interpretive risk (coverage start, partial vs complete cost basis, nulls). For a single-parameter read tool with full annotations this is close to complete. Missing only notes on ordering, empty-result behavior, or tickers outside the covered universe.

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?

There is a single parameter, `ticker`, and schema description coverage is 100%, so the schema already documents it with an example. The description adds nothing about ticker format, casing, exchange suffixes, or invalid-ticker handling, so it neither compensates nor detracts. Baseline 3 applies.

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 verb and resource: 'per-insider position aggregates for a ticker: which insiders hold positions in the stock and their aggregate cost and value, derived from Form 4 filings.' The scope (aggregates, per-insider, cost and value) is precise. It never differentiates itself from close siblings such as get_insider_positions, get_insider_transactions, or get_insider_cluster_buys, so an agent cannot route between them from this text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use statement and no named alternatives, despite a dense cluster of insider-related siblings. The coverage-window caveat ('since coverageStart') implies this is a longitudinal aggregate view rather than a transaction log, but the agent must infer that and receives no exclusions or prerequisites to guide selection.

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

Deploy Server

Other Tools