Docs menuexpand_more
MCP tool
get_dividends
Key points
- check_circleIt maps to the REST endpoint /stable/dividends, 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 dividend history of a stock, newest first, including company forecasts. Dividends are per share in JPY.
Description sent to AI clients
Dividend history with ex-dividend date, payment date, announcement date, and split-adjusted amount. Includes forecasts (forecastOrActual). 配当履歴（権利落ち日・支払日・分割調整後金額・予想/実績区分）。
The model reads this description to choose the tool. It is written in both English and Japanese.
What you can answer with it
- chatReview past dividends to judge stability
- chatCheck the forecast dividend to estimate yield
- chatList dividends of your holdings to estimate annual income
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 40, max 100)Default: 40Range: 1–100 |
REST endpoint
This tool calls /stable/dividends. Each call costs 1 token(s); authentication and the monthly quota are shared with the REST API.
GET /stable/dividends1 token(s)Examples
Example prompt
Using ZENITH Code data, help me with this: Review past dividends to judge stability
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_dividends",
"arguments": {
"symbol": "7203"
}
}
}The same data over REST:
curl "https://api.zenithcode.net/stable/dividends?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_dividends?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_dividends cost per call?expand_more
1 token(s), the same as calling /stable/dividends directly.
Can I show get_dividends 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_dividends return?expand_more
Returns the dividend history of a stock, newest first, including company forecasts. Dividends are per share in JPY.
How can I verify the source of get_dividends 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/dividends API docs.
Which tools are used together with get_dividends?expand_more
Common companions are get_dividend_changes, get_dividend_streaks, get_dividends_calendar. 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.