Retrieve corporate actions for any NSE symbol: dividends, bonus, splits, rights, buybacks, with ex-dates and record dates, plus upcoming board meetings.
Dividends, bonus, splits, rights and buybacks with ex-dates and record dates (NSE), plus upcoming and recent board meetings (results dates etc.).
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden. It usefully scopes the data to NSE and distinguishes upcoming versus recent board meetings, but it does not state return format, time windows, pagination, or any limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence with no filler; every listed item carries meaning. It could be more structured with an explicit verb, but it is appropriately concise and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool, the description conveys the main content well and notes the NSE scope. However, it omits any mention of the symbol parameter, and with no output schema it only partially substitutes for return-value documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one required symbol parameter with no description and 0% schema coverage, and the description never mentions the symbol parameter or how it filters the corporate actions. The meaning of 'symbol' is standard, but the description adds no parameter-level semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names the resource concretely: dividends, bonus, splits, rights, buybacks, and board meetings with ex-dates and record dates. It is clearly distinct from generic siblings like get_announcements or get_stock_quote, though it lacks an explicit verb such as 'Retrieves'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives, and there are no exclusions or references to related tools. The description defines the content but leaves the selection conditions to the agent's inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.