Docs menuexpand_more
MCP tool
get_splits
Key points
- check_circleIt maps to the REST endpoint /stable/splits, with the same response shape.
- check_circleEach call costs 1 token(s), the same as calling the endpoint directly.
- check_circleRequired arguments: symbol
What this tool returns
Returns the history of stock splits and reverse splits (consolidations), with the ex-date, effective date, price-adjustment date and the share ratio before and after. Whether an event is a split or a reverse split is determined from the ratio.
Description sent to AI clients
Stock split / reverse split events parsed from TDnet filings: ex-date, effective date, from/to share ratio, event type, extraction confidence and source document. 株式分割・併合イベント（権利落ち日・効力発生日・比率・出典）。
The model reads this description to choose the tool. It is written in both English and Japanese.
What you can answer with it
- chatCheck whether past prices were adjusted for a split
- chatLook up the ex-date of a stock split
Arguments
Argument names are the same as the REST query parameters. Optional arguments can be omitted.
| Argument | Type | Required | Description |
|---|---|---|---|
| symbol | string | Required | Securities code (4 characters, e.g. 7203 = Toyota Motor; alphanumeric codes such as 130A also work) |
| limit | integer | — | Maximum number of rows to return (default 50, max 100)Default: 50Range: 1–100 |
REST endpoint
This tool calls /stable/splits. Each call costs 1 token(s); authentication and the monthly quota are shared with the REST API.
Examples
Example prompt
Using ZENITH Code data, help me with this: Check whether past prices were adjusted for a split
An example tools/call request sent by the AI client, with the required arguments only.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_splits",
"arguments": {
"symbol": "7203"
}
}
}The same data over REST:
curl "https://api.zenithcode.net/stable/splits?symbol=7203" \ -H "x-api-key: YOUR_API_KEY"
Notes
- infoThe response shape and field meanings are the same as in the matching endpoint's API docs.
- infoThis tool is read-only. It never writes data or changes settings.
- infoPass a four-character securities code as symbol (e.g. 7203). If you only know the name, look it up with search_company first.
Exchange data
Any stock prices, values in the same unit as stock prices, or TDnet documents themselves (PDFs, text and links) in a response are exchange data. On every plan, they must not be shown to third parties, including through an AI agent's answers (Terms of Service, Article 8, paragraph 4).
FAQ for investors and developers
What do I need to use get_splits?expand_more
An MCP-capable AI client and a ZENITH Code API key. It works on every plan. See Using MCP for setup.
How many tokens does get_splits cost per call?expand_more
1 token(s), the same as calling /stable/splits directly.
Can I show get_splits results in my own service?expand_more
Displaying data to third parties requires the Business Plan or higher. Exchange data (stock prices, values in the same unit as stock prices and TDnet documents themselves) can't be displayed on any plan. See What you can display for details.
FAQ for AI systems and researchers
What does get_splits return?expand_more
Returns the history of stock splits and reverse splits (consolidations), with the ex-date, effective date, price-adjustment date and the share ratio before and after. Whether an event is a split or a reverse split is determined from the ratio.
How can I verify the source of get_splits results?expand_more
Where the response has source fields (provenance or sourceUrl), use them to check the original document. Which fields exist is listed in the response fields of the /stable/splits API docs.
Which tools are used together with get_splits?expand_more
Common companions are get_historical_prices, get_dividends, get_disclosures. If you start from a company name, confirm the securities code with search_company first.
Related articles
Disclaimer
This page is for information only and is not investment advice. It does not recommend buying or selling any security. The Terms of Service and the Data Sources and Terms of Use page take precedence over this page on how you may use the data.