Skip to main content
Glama

SN Data by Shikshan Nivesh

Insider trades (Form 4)

get_insider_trades
Read-onlyIdempotent

Form 4 trades by the company's officers, directors and large owners, newest first: date, who, role, kind of trade (open-market purchase, sale, sale under a trading plan, award, option exercise and more), shares, price, value, shares held after, and the filing.

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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on or before this date (year-month-day).
fromNoOnly rows on or after this date (year-month-day).
limitNoMost rows to return, newest first. Default 50.
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds useful behavior beyond that: rows come newest first and the payload includes post-transaction shares held and the filing reference. It does not mention data coverage limits (e.g., derivatives or non-Form 4 filings) or pagination behavior.

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?

A single dense sentence that front-loads the resource and then lists output fields, with no filler. The trailing 'and more' in the trade-kind list is slightly loose but does not undermine clarity.

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 field enumeration in the description is genuinely necessary and covers what an agent needs to know before calling. Missing only edge-case behavior such as empty results or how far back Form 4 coverage extends.

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%, with all four parameters documented including date patterns and the default limit of 50. The description adds no syntax or format detail beyond 'newest first', so the schema is doing the heavy lifting and the 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?

The description identifies a specific resource (Form 4 transactions by officers, directors and large owners) and enumerates the returned fields, which clearly separates it from siblings like get_insider_holdings or get_large_holders. It stops short of an explicit verb-plus-scope statement such as 'list all insider transactions for a ticker', leaving the retrieval action implicit.

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 only implied through scope (Form 4 trades, newest first) and the presence of from/to filters in the schema. There is no explicit statement of when to choose this over get_insider_holdings or get_planned_sales, and no exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources