Worldschedule
by Distribusion Technologies (Community)
Description
Your global companion for bus and train travel. Skip the complex search filters. Just say where you want to go, and it handles the rest using the network of 2,500+ carriers covering 40K+ cities & airports in 100+ countries. From airport transfers to cross-country rail, find the best routes and book your tickets instantly in one seamless conversation. - Global Coverage: Access thousands of bus and train routes worldwide - Simple Booking: Go from \"Where should I go?\" to a confirmed ticket in a few moments - Live Data: Get real-time pricing and availability directly from the carriers
Capabilities
No special capabilities listed
AI Agent Discovery
Worldschedule is indexed by Tedix as a structured travel listing for AI assistants, search crawlers, and users comparing agent-ready apps.
- Worldschedule is categorized as Travel.
- Developer: Distribusion Technologies.
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: chatgpt.
- Available regions: US, FR, GB, ES, KR, IN.
Use this page to understand whether Worldschedule is relevant for travel workflows in AI assistants.
For MCP discovery, this listing helps crawlers connect Worldschedule to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.
The canonical Tedix directory URL is https://tedix.dev/apps/worldschedule/.
Crawlable Profile
Source and availability
Tedix identifies Worldschedule from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory. Availability is reported for US, FR, GB, ES, KR, IN.
- ChatGPT app store Auth not flagged · RELEASED · US, FR, GB, ES, KR, IN
Auth, tools, and actions
Authentication: Open Access. No special capability flags are currently listed. Current MCP inventory reports 4 tools, 3 resources, and 0 prompts.
- Connections Find · Read-only action
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.
- Get Vacancies · Read-only action
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.
- Price Calendar · Read-only action
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.
- Search Locations · Read-only action
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.
Verification freshness
- Catalog synced 11h ago (June 6, 2026)
- Connector checked 2d ago (June 4, 2026)
- MCP scanned 2d ago (June 4, 2026)
- Website enriched 2d ago (June 4, 2026)
- Directory updated 11h ago (June 6, 2026)
Alternatives and related apps
Comparable apps in Travel include 12Go, ADAC Mietwagen, ALL Accor, AbhiBus.
Publisher Intelligence
Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.
Server Status App for finding and booking trips v1.27.0
https://worldschedule.ai/mcp Last checked: 2d ago
Technical Details
Tools(4)
Showing 4 of 4 tools
| Tool | Description | Flags | Test | Last Tested | |
|---|---|---|---|---|---|
connections-find | 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. | read-only | 100%Latency 1.2s | 2d ago | |
get-vacancies | 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. | read-only | 100%Latency 690ms | 2d ago | |
price-calendar | 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. | read-only | 100%Latency 1.2s | 2d ago | |
search-locations | 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. | read-only | 100%Latency 1.0s | 2d ago |
Discoverability Score
Fair
57 of 100 — how easily AI agents find your app
- Description quality20/20
- Example prompts0/20
- Keyword coverage0/15
- Tool metadata16/20
- Visual assets8/20
- Endpoint health10/10
- Data freshness15/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Open Access
- Listed on
- ChatGPT
- Added
- June 3, 2026
- Last synced
- 11h ago
- Last checked
- 2d ago
- Version
- 1.27.0
- Distribution
- Ecosystem Directory
