Docs menuexpand_more
MCP tool
get_extraordinary_report_reasons
Key points
- check_circleIt maps to the REST endpoint /stable/extraordinary-report-reasons, with the same response shape.
- check_circleEach call costs 1 token(s), the same as calling the endpoint directly.
- check_circleRequired arguments: none
What this tool returns
Returns the list of reason keys used to classify extraordinary reports, with Japanese and English labels. It covers M&A decisions, changes of parent or major shareholders, stock options, auditor and representative changes, disasters and more. Use a key as reason in /stable/extraordinary-reports. Reports whose element is not listed get a key converted automatically, so some keys may not appear in this list.
Description sent to AI clients
List the reason keys that classify EDINET extraordinary reports (臨時報告書) — absorption_merger, share_exchange, major_shareholder_change, stock_option_issue, auditor_change, disaster_damage … — with Japanese/English labels and category. Use a key as `reason` in get_extraordinary_report_events. 臨時報告書の提出事由マスタ（日英ラベル）。get_extraordinary_report_events の reason に指定する key の一覧。
The model reads this description to choose the tool. It is written in both English and Japanese.
What you can answer with it
- chatLook up valid reason keys before filtering reports
- chatShow reason names as filter options in your UI
Arguments
Argument names are the same as the REST query parameters. Optional arguments can be omitted.
| Argument | Type | Required | Description |
|---|---|---|---|
| category | stringreorganization | ownership | capital-and-financing | governance | significant-event | fund | — | Filter by category (reorganization, ownership, capital-and-financing, governance, significant-event, fund). Omit for all |
REST endpoint
This tool calls /stable/extraordinary-report-reasons. 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: Look up valid reason keys before filtering reports
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_extraordinary_report_reasons",
"arguments": {}
}
}The same data over REST:
curl "https://api.zenithcode.net/stable/extraordinary-report-reasons" \ -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.
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_extraordinary_report_reasons?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_extraordinary_report_reasons cost per call?expand_more
1 token(s), the same as calling /stable/extraordinary-report-reasons directly.
Can I show get_extraordinary_report_reasons 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_extraordinary_report_reasons return?expand_more
Returns the list of reason keys used to classify extraordinary reports, with Japanese and English labels. It covers M&A decisions, changes of parent or major shareholders, stock options, auditor and representative changes, disasters and more. Use a key as reason in /stable/extraordinary-reports. Reports whose element is not listed get a key converted automatically, so some keys may not appear in this list.
How can I verify the source of get_extraordinary_report_reasons 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/extraordinary-report-reasons API docs.
Which tools are used together with get_extraordinary_report_reasons?expand_more
Common companions are get_extraordinary_report_events, get_events_feed, 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.