Skip to main content
Glama
screener-mcp
by LogeshR15

get_insider_trading

Read-only

Fetch recent SEBI PIT insider trading disclosures for an NSE company, including promoter/KMP buys and sells with quantity, value, and holdings before/after; merges NSE feeds to capture missed filings.

Instructions

Recent insider trading disclosures (SEBI PIT Regulation 7(2)) for a company.

Shows promoter/KMP/designated-person trades — buy or sell, quantity, value, and holding before/after — with no minimum trade size. This is different from get_bulk_deals, which only catches single trades over 0.5% of equity and so misses most insider activity. Merges NSE's two PIT feeds (each lists filings the other doesn't).

symbol: NSE trading symbol (e.g., "RELIANCE", "INFY") days: look-back window (default 365)

Examples: get_insider_trading("RELIANCE") get_insider_trading("ADANIENT")

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": {
      "symbol": "<symbol>"
    },
    "name": "get_insider_trading"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely non-obvious behavior by disclosing that it merges NSE's two PIT feeds, each of which lists filings the other omits. It also lists the returned fields and the absence of a size threshold. It does not mention latency, rate limits, or staleness of the feeds, which keeps it from 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?

Front-loaded with the resource, then the sibling differentiation, then parameter notes, then examples — a sensible order with no filler. The Examples block is somewhat redundant with the parameter examples already inline, which keeps it just short of a 5.

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-format detail is not required, and annotations cover the safety profile; the description still adds the returned field list for orientation. For a two-parameter read tool this is nearly complete, with only minor gaps around feed freshness and maximum look-back windows.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning, and it does: `symbol` is defined as an NSE trading symbol with concrete examples ("RELIANCE", "INFY"), and `days` is defined as a look-back window with default 365, matching the schema default. Only edge cases (maximum window, invalid symbol behavior) are left unspecified.

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 (recent insider trading disclosures per SEBI PIT Regulation 7(2)) and immediately scopes the content: promoter/KMP/designated-person trades with buy/sell, quantity, value, and holding before/after. It explicitly contrasts itself with `get_bulk_deals`, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Provides an explicit routing rule: this tool has no minimum trade size, whereas `get_bulk_deals` only catches single trades over 0.5% of equity and therefore misses most insider activity. That single sentence tells the agent both when to prefer this tool and why the alternative is insufficient, and the usage examples reinforce the intended call pattern.

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