Skip to main content
Glama

nse_insider_trading

Retrieve SEBI-mandated insider trading and SAST disclosures for NSE stocks, showing buy vs sell counts, insider sentiment, and transaction details.

Instructions

NSE insider trading and SAST (substantial acquisition) disclosures for a stock.

Covers features Trendlyne (₹4,950/yr) and Screener Pro (₹4,999/yr) charge for — free here.

Shows:

  • All SEBI-mandated insider trading disclosures from NSE

  • Buy vs sell transaction count

  • Insider sentiment summary

  • Acquirer/seller name, shares traded, dates

Args: symbol: NSE stock symbol (e.g., RELIANCE, TCS, INFY, HDFCBANK) days: Lookback period in days (default 90, max ~365)

Examples: nse_insider_trading("RELIANCE") → Last 90 days insider activity for Reliance nse_insider_trading("TCS", 180) → Last 6 months insider trades for TCS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions free access and lookback max ~365 days, but does not cover rate limits, auth requirements, symbol case-sensitivity, or error handling.

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?

Description is structured with bullet points and examples, making it scannable. A few sentences could be tightened, but overall efficient and front-loaded.

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 output schema exists, return values are covered. Description explains data fields, parameters, and unique value. No major gaps for a data retrieval tool.

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?

With 0% schema coverage, the description adds significant value: explains symbol as NSE stock symbol with examples, days as lookback period with default and max. Examples illustrate usage.

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 clearly states it shows NSE insider trading and SAST disclosures for a stock, listing specific data points. It implies a unique value proposition (free vs paid tools) but does not explicitly contrast with sibling tools like 'get_insider_signal'.

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?

The description implies usage for accessing insider trading data for NSE stocks, but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_insider_signal). No when-not or exclusions provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/finstacklabs/finstack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server