Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Corporate action and economic calendar

corpaction_calendar
Read-onlyIdempotent

Retrieve scheduled corporate actions and economic calendar events for a specific date, including dividends, stock splits, rights issues, IPOs, and AGMs, with optional symbol filtering.

Instructions

Everything scheduled on a date: dividends (cum/ex/payment), stock splits, rights issues, bonus, IPOs, RUPS/AGMs, public expose, plus economic calendar events.

Returns (Stockbit's data field): data keyed by category: economic[{econcal_item, econcal_time, econcal_date, econcal_month, econcal_actual, econcal_forecast, econcal_previous}], dividend[{company_symbol, dividend_value_formatted, event_note}], stocksplit/stock_reverse[{company_symbol, stocksplit_ratio, event_note}], rightissue[{company_symbol, rightissue_price_formatted, event_note}], warrant[{company_symbol, wrant_exc_price_formatted, event_note}], bonus[{company_symbol, sahambonus_ratio, event_note}], tender[{company_symbol, tender_price, event_note}], rups[{company_symbol, rups_time}], pubex[{company_symbol, puexp_time}], ipo[{company_name, company_symbol, ipo_data_detail{price_formatted}, ipo_listing_date}], stock_divid…

Endpoint: GET exodus /corpaction.

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": {
      "date": "<date>"
    },
    "name": "corpaction_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD
symbolNo'' for market-wide Default "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's added value is the per-category return shape, which is genuinely useful, but it says nothing about permissions, rate limits, empty-category behavior, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is well front-loaded and dense with useful categories. The second sentence, however, is a long comma-separated field dump that terminates mid-word ('stock_divid…'), which reads as truncated tooling output rather than an authored explanation and hurts scanability.

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?

With no output schema, the description correctly takes on the burden of describing the returned category keys and their fields, which is the right call for a calendar tool spanning ten-plus event types. It only falls short on the truncated final category and on unstated behavior when a date has no events.

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%: date carries the 'YYYY-MM-DD' format and symbol documents the empty-string default for market-wide queries. The description adds no further parameter meaning beyond what the schema already states, so the baseline 3 applies.

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 names a concrete resource (corporate action + economic calendar events for a given date) and enumerates the covered event categories: dividends with cum/ex/payment phases, splits, rights issues, bonus, IPOs, RUPS/AGMs and public expose. An agent can tell what it returns without opening the schema. It stops short of distinguishing itself from siblings such as corpaction_by_category or price_corp_action_marks.

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?

Usage is only implied by the phrase 'Everything scheduled on a date', which suggests a date-first, all-categories lookup. There is no explicit when-to-use or when-not-to-use statement and no pointer to the category-scoped or price-mark siblings, leaving the agent to infer routing between four corpaction tools.

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

Deploy Server

Other Tools