Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

corporate_actions

Read-only

Retrieves IDX corporate action records by type—dividends, rights issues, RUPS, splits, tender offers, warrants, IPOs, or the economic calendar—for one ticker's history or the whole market.

Instructions

Corporate actions of ONE kind: dividends, rights issues, RUPS (shareholder meetings), bonus shares, splits, reverse splits, tender offers, warrants, public expose, IPOs, or the economic-events calendar. Pass symbol for one issuer's history of that action, or omit it for the market-wide list. An empty rows with rowsFrom: "data" is a real answer, but it means NONE IN THE PERIOD THIS FEED COVERS — nothing in the response says where that period starts, so an empty page is 'none on record here' and is NOT evidence the issuer never did it. action_type is a closed list and an unknown one is rejected here rather than sent, because the endpoint answers an unknown kind with an empty page that reads like a quiet calendar. warrant is a corporate action on the ISSUER's own share count. A structured call warrant — the separately listed instrument a securities house issues against a stock under its own ticker — is not one, and nothing here ties such a ticker back to its underlying. An empty warrant list therefore answers for the issuer alone: it is not evidence that no warrant trades on the symbol. suspectDates appears only when a row's own dates are in an order that cannot have happened — a RUPS record date after the meeting it gates, a cum date after its ex-date, a payment before the record date. That is UPSTREAM data being wrong, not a failure here: the row is still returned exactly as Stockbit sent it, and each entry names both wire keys and both values so you can judge the pair yourself — the values NORMALIZED to YYYY-MM-DD, not the wire strings, so read the row itself to see what was actually sent. The key spellings are candidates, so a suspicion can be a misread field rather than a bad date. Absent means nothing was out of order — it does NOT mean the dates were checked and cleared, because most rows carry neither side of any pair. For dividends prefer dividend_calendar, which also covers stock dividends.

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": {
      "action_type": "<action_type>"
    },
    "name": "corporate_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows. Omitted entirely when not given
symbolNoIDX ticker, e.g. BBRI. Omit for the whole market
action_typeYesWhich action kind, e.g. dividend, rightissue, rups. `tender` and `stock_reverse` — the two spellings calendar_today tags rows with — are accepted and translated to `tenderoffer` and `reversesplit`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it explains that an empty `rows` with `rowsFrom: "data"` means 'none in the period this feed covers' and is not proof of absence, that `warrant` covers issuer share-count actions only and not listed structured warrants, and that `suspectDates` signals upstream date-ordering errors with rows still returned as sent. These are exactly the failure-mode disclosures an agent cannot get from annotations.

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 purpose and scope, and nearly every sentence carries a distinct caveat. It is long for a three-parameter read tool, and the `suspectDates` paragraph in particular is dense and partly redundant ('Absent means nothing was out of order — it does NOT mean the dates were checked and cleared'), costing it a point.

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 no output schema, the definition does a good job defining the meaningful return signals (`rows`, `rowsFrom`, `suspectDates`) and their interpretation. It stops short of describing the row fields an agent would actually read, and the `rowsFrom` envelope is only referenced, never explained.

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 100%, so the baseline is 3; the description still adds meaning by clarifying the scope implied by omitting `symbol` and by explaining that `action_type` is a closed list enforced client-side rather than server-side. The alias translation for `tender`/`stock_reverse` is already in the schema, so no credit is taken for it.

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?

Opens with a specific verb+resource ('Corporate actions of ONE kind') and enumerates the exact kinds covered. It also states the two scoping modes (per-issuer via `symbol`, market-wide when omitted), so an agent knows precisely what this tool returns without opening the 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?

Gives explicit routing: 'Pass `symbol` for one issuer's history... or omit it for the market-wide list,' and names an alternative with its advantage: 'For dividends prefer `dividend_calendar`, which also covers stock dividends.' It also explains that an unknown `action_type` is rejected here rather than sent, which prevents a silent-empty-page mistake.

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