Docs menuexpand_more
MCP tool
get_delisting_schedule
Key points
- check_circleIt maps to the REST endpoint /stable/delisting-schedule, 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 scheduled, completed and cancelled delistings of Japanese listed companies together with the source TDnet disclosure. If from is omitted, delisting dates from today onward are returned.
Description sent to AI clients
Scheduled and completed delistings of Japanese listed companies with delisting date, status and source TDnet document. Defaults to delisting dates from today onward. 上場廃止予定の一覧（省略時は本日以降）。
The model reads this description to choose the tool. It is written in both English and Japanese.
What you can answer with it
- chatRegularly check whether any of your holdings is scheduled for delisting
- chatList upcoming delistings caused by tender offers or mergers
- chatReview delistings that were cancelled
Arguments
Argument names are the same as the REST query parameters. Optional arguments can be omitted.
| Argument | Type | Required | Description |
|---|---|---|---|
| from | string | — | Earliest delisting date (YYYY-MM-DD). Defaults to today |
| to | string | — | Latest delisting date (YYYY-MM-DD) |
| status | stringscheduled | applied | cancelled | — | Filter by status: scheduled, applied or cancelled |
| limit | integer | — | Maximum number of rows to return (default 200, max 500)Default: 200Range: 1–500 |
REST endpoint
This tool calls /stable/delisting-schedule. 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: Regularly check whether any of your holdings is scheduled for delisting
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_delisting_schedule",
"arguments": {}
}
}The same data over REST:
curl "https://api.zenithcode.net/stable/delisting-schedule" \ -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_delisting_schedule?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_delisting_schedule cost per call?expand_more
1 token(s), the same as calling /stable/delisting-schedule directly.
Can I show get_delisting_schedule 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_delisting_schedule return?expand_more
Returns scheduled, completed and cancelled delistings of Japanese listed companies together with the source TDnet disclosure. If from is omitted, delisting dates from today onward are returned.
How can I verify the source of get_delisting_schedule 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/delisting-schedule API docs.
Which tools are used together with get_delisting_schedule?expand_more
Common companions are get_disclosures, get_extraordinary_report_events, get_events_feed. 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.