Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Corporate actions by category

corpaction_by_category
Read-onlyIdempotent

Fetch corporate actions for a specific category—such as dividends, stock splits, rights issues, warrants, bonuses, tender offers, IPOs, or economic events—market-wide or filtered by ticker.

Instructions

Corporate actions of one category (e.g. dividend, rups, stocksplit, rightissue, warrant, bonus, tenderoffer, ipo, economic), market-wide or for one symbol (symbol).

Returns (Stockbit's data field): data{: [...]} - key equals category except reversesplit->stock_reverse and tenderoffer->tender. Field families: dividend_{id,type,value,value_formatted,cumdate,exdate,recdate,paydate,yield,amount,per_share,currency,...}, stocksplit_{old,new,factor,ratio,cumdate,exdate,recdate,paymentdate}, rightissue_{old,new,ratio,factor,price,cumdate,exdate,recdate,trading_start,trading_end}, wrant_{exc_price,exc_from,exc_end,trading_from,trading_end}, sahambonus_{id,ratio}, tender_{price,start,end,paydate,shares,percentage,offer}, rups_{date,time,venue,eligible_date}, puexp_{date,time,venue}, econcal_{item,date,time,month,actual,forecast,previous}; plus company_symbol, event_note

Endpoint: GET exodus /corpaction/{categoryName}.

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": {
      "categoryName": "<categoryName>"
    },
    "name": "corpaction_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoTicker; '' (empty) for the market-wide calendar list Default "".
categoryNameYesUI maps stock_reverse->reversesplit and tender->tenderoffer. 'economic' is the ECONOMIC CALENDAR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With readOnly/idempotent/openWorld annotations already covering the safety profile, the description adds real value by disclosing the return envelope (data{<category>: [...]}) and the key-remapping rule (reversesplit->stock_reverse, tenderoffer->tender) that an agent cannot infer. It also names the endpoint, which is useful for debugging, but says nothing about pagination, coverage window, or rate limits.

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?

Purpose is front-loaded in the first clause, followed by returns and endpoint — a sensible order. The field-family enumeration is long, but since there is no output schema, most of it earns its place; a few of the trailing '...' families are near-redundant padding.

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 two-parameter tool with no output schema, the description supplies the return structure, key naming quirks, and per-category field families, which is close to sufficient. The main residual gap is the usable category list being introduced with 'e.g.' and omitting variants like reversesplit at the call site rather than only in the return section.

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 already 100%, so the baseline is 3, but the description adds the valid category value set and the read-side key remapping that complements the schema's write-side mapping note ('UI maps stock_reverse->reversesplit'). This meaningfully lowers the chance of an agent passing a category name whose returned key differs.

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 states a specific verb+resource ('Corporate actions of one category') and its scope (market-wide or one symbol), and enumerates category values (dividend, rups, stocksplit, rightissue, warrant, bonus, tenderoffer, ipo, economic). It does not explicitly contrast itself with the sibling corpaction_calendar, though the schema note about the 'market-wide calendar list' partially covers that.

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 implied: pass a category for a category-specific action, pass a symbol for one ticker or leave it empty for the market-wide list. There is no explicit when-to-use/when-not guidance or named alternative for the calendar-type queries that the sibling corpaction_calendar likely serves.

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