Worldschedule

Search for available connections (trips) between station, city or area codes. Resolve codes with the search-locations tool first (returns city, station, and area matches). Station codes are 8-letter codes, city codes are 5-letter codes, area codes are 7-letter codes. Departure location parameters (city, area and stations) are mutually exclusive. Arrival location parameters (city, area and stations) are mutually exclusive. Code types can be different for departure and arrival, for example: - departure: station codes, arrival: city code - departure: area code, arrival: city code - departure: city code, arrival: city code - departure: city code, arrival: station codes - etc. Departure start time (default: 00:00) is the earliest departure time for the connections searched. Each connection in structuredContent.connections is a full record (index, stations, times, carrier, fare class, segments). When the user picks one by index (#1, first, cheapest, etc.), use that record for get-vacancies — do not ask them to search again. When calling this tool: Final answer only. No progress updates, no tool commentary, and no interim status messages.

connections-find

Check if a specific connection is still available and get its current price. Call this immediately when the user picks a connection by index (#1, first, cheapest, etc.). The full connection object is already in structuredContent.connections from the latest connections-find call — each entry has an index field. Find the matching connection and map its fields to this tool (e.g. departure_station.code → departureStationCode, departure_time → departureTime, marketing_carrier_code → marketingCarrierCode, fare_class → fareClass, fare_class_code → fareClassCode). Times are ISO (YYYY-MM-DDTHH:MM). Do NOT ask the user to search again or say you lack the connection payload when connections-find already returned results in this conversation. When calling this tool: Final answer only. No progress updates, no tool commentary, and no interim status messages.

get-vacancies

Get minimum prices per day for a route. Resolve departure and arrival codes with search-locations first (city, station, or area types). Station codes are 8-letter codes, city codes are 5-letter codes, area codes are 7-letter codes. Departure location parameters (city, area and stations) are mutually exclusive. Arrival location parameters (city, area and stations) are mutually exclusive. Departure date range (start and end date) is required. Marketing carrier codes (optional) are used to filter connections. When calling this tool: Final answer only. No progress updates, no tool commentary, and no interim status messages.

price-calendar

Search for locations (cities, stations, areas including airports) by text query via the Suggestion Service API. Each result includes type (city, station, or area), code, name, and score. Use the type to map codes to connections-find and price-calendar: - city → fromCityCode/toCityCode or fromCity/toCity (5-letter codes) - station → fromStationCodes/toStationCodes or departureStationCode/arrivalStationCode (8-letter codes) - area → fromAreaCode/toAreaCode (7-letter codes, e.g. airports) Prefer limit=5 for breadth, then pick the best match from context. If a locale returns few results, try again with locale 'en'. When calling this tool: Final answer only. No progress updates, no tool commentary, and no interim status messages.

search-locations