Skip to main content
Glama

TejHQ Indian Markets

Corporate actions

actions
Read-onlyIdempotent

Corporate actions for one symbol across all years: dividends, splits, bonuses and rights, with ex dates, ratios and amounts, newest first. Required: symbol. Up to 100 rows per call. End of day data only, no intraday or live prices. No API key needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost rows to return.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
symbolYesExchange ticker, for example RELIANCE, TCS, M&M. Case does not matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 100-row ceiling, newest-first ordering, EOD-only data freshness, and the absence of an auth requirement.

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?

Three short sentences, front-loaded with what the tool returns before listing constraints. No filler, no repetition of the title, and every clause carries information an agent can act on.

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?

There is no output schema, but the description compensates by naming the returned fields and their ordering, and paging is covered by the schema's next_offset note. For a simple read-only lookup with a 3-parameter schema this is nearly complete, with only the exact response envelope left unstated.

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?

Schema description coverage is 100%, so all three parameters (symbol, limit, offset) are already documented in the schema, including the meta.next_offset paging hint. The description restates that symbol is required and that at most 100 rows come back, but adds no new meaning about limit or offset — baseline 3 applies.

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 resource (corporate actions for one symbol) and enumerates exactly what is returned — dividends, splits, bonuses, rights with ex dates, ratios and amounts — plus the ordering (newest first). That is enough for an agent to distinguish it from price-oriented siblings like ohlcv or adjusted without opening any schema.

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

Usage Guidelines4/5

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

Gives concrete usage context: symbol is required, results cap at 100 rows per call, data is end-of-day only with no intraday or live prices, and no API key is needed. The 'no intraday or live prices' clause implicitly steers the agent away from this tool for live quotes, but no sibling tool is named as the explicit alternative.

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