Feature: MCP Server Tool to Assess and find Train Connections

[abeckDev]

Feature Request: Develop a Tool for MCP Server to Assess Train Connections

Objective:
Enable the MCP server for the Timetable API to provide a tool that takes a current station (A) and a destination station (B) as input. The tool should:

1. Validate inputs by determining the correct EVA IDs and full names of both stations.
2. Identify which trains regularly operate between station A and station B (A and B can be any station along the train's line).
3. If multiple options are available, query current schedule changes (disruptions, delays, reroutes, etc.).
4. Output for user: list of viable train connections, including which one to choose and the expected current delays due to disruptions or schedule changes.

---

Context and Data Examples:

• timetable_schema.json: Shows the schema for timetable data returned by the Timetable API. Includes explanations for stop elements, messages, delays, etc.
• recent_changes.xml: Example output of the current changes task. Shows how modifications, messages, and delays are reflected as additional XML attributes/objects in timetable schemas.
• regular_schedule_byhour.xml: Example of the regular schedule board for one station and one hour. Shows the normal (unchanged) timetable for context.

Requirements:

• Tool interface should accept user station input in natural language, resolve station EVA IDs and full names.
• Implements logic to find all train lines connecting A to B given current schedule.
• Integrates disruption/delay checking from recent_changes sources and timetable messages.
• Output selection should include best train (minimal delay, time, etc.) and a summary of delay/disruption status for each option.

---

Why?

This tool will improve the usability and value of the Timetable API by providing actionable train selection advice given the real-time situation, rather than just raw data.