Skip to main content
Glama

SN Data by Shikshan Nivesh

Insider holdings (Forms 3, 4 and 5)

get_insider_holdings
Read-onlyIdempotent

What each of the company's insiders last reported holding, newest first: who, role, the security, held directly or how it is held (a trust, a spouse), shares, the date 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_holdings"
  }
}

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.6/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, so the safety profile is covered. The description goes beyond them usefully by disclosing the shape of the result — one latest-reported position per insider including indirect/trust holdings — which matters because there is no output schema. It does not discuss ordering guarantees under date filters or whether multiple rows can exist per insider.

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?

A single front-loaded sentence with zero filler; the colon list of returned fields is scannable and the parenthetical '(a trust, a spouse)' clarifies indirect ownership in three words. Nothing here needs trimming.

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 simple four-parameter read tool with full schema coverage and complete safety annotations, the definition gives enough to call it and to interpret the rows. The remaining gap is that the title's 'Forms 3, 4 and 5' framing never appears in the description, so an agent cannot tell whether amendments or older filings are represented.

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?

With 100% schema description coverage, the schema already explains ticker, from, to and limit. The description adds only the redundant 'newest first' ordering cue and no extra detail on date-filter interaction or what happens at the 500-row cap, so 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 names the specific resource and scope: what 'each of the company's insiders last reported holding', returned newest first, with an enumerated field list (who, role, security, direct/indirect holding, shares, date, filing). That implicitly separates it from a transaction list, but it never names the obvious sibling get_insider_trades, so an agent must infer the snapshot-vs-flows distinction.

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?

There is no when-to-use guidance at all: no mention of when to pick this over get_insider_trades, get_planned_sales, or get_large_holders, and no stated preconditions. The phrase 'last reported holding' hints at a current-snapshot use case but no alternative is named or excluded.

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