finstack-mcp

nse_corporate_actions

Retrieve corporate actions including dividends, stock splits, and bonuses for any NSE stock. See historical events with dates and values.

Instructions

Get corporate actions for an NSE stock — dividends, stock splits, bonuses.

Shows recent and historical corporate actions with dates and values.

Args: symbol: NSE stock symbol (e.g., ITC, RELIANCE, TCS, COALINDIA)

Examples: nse_corporate_actions("ITC") → ITC dividends and splits nse_corporate_actions("RELIANCE") → Reliance corporate actions

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": "nse_corporate_actions"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Mar 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations are absent, so the description is the sole source. It notes that recent and historical actions are shown with dates and values, which gives some insight into behavior, but doesn't mention any limitations, error cases, or whether data is real-time.

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?

The description is well-structured with a clear main verb, a brief output summary, and a parameter section with examples. Slightly redundant between the first two sentences but remains tight.

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 single-parameter tool with an output schema provided, the description covers the input, output features, and examples adequately. It only misses guidance on selecting this tool among sibling tools, which is already reflected in the usage guidelines dimension.

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%, but the description thoroughly explains the symbol parameter with format examples (ITC, RELIANCE) and states it expects an NSE symbol, adding value beyond the raw schema.

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 retrieves corporate actions (dividends, splits, bonuses) for an NSE stock, with examples. It distinguishes itself from simple quote tools but doesn't explicitly differentiate from sibling tools like dividend_history, so it's clear but not fully differentiated.

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 mention of when to use this tool versus alternatives such as dividend_history or nse_quote. The examples show usage but no exclusions or context for choosing it over related tools.

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

Deploy Server