Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UK_TRANSPORT_APP_ID | No | Your UK Transport API app ID | |
| UK_TRANSPORT_API_KEY | No | Your UK Transport API key |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ch_search_connections | Search for train connections in Switzerland between two stations. Uses transport.opendata.ch API to provide real-time connection data including departure times, duration, platforms, and transfers. |
| ch_search_stations | Search for Swiss train stations by name or location. |
| ch_get_departures | Get departure board for a Swiss train station with real-time information. |
| ch_nearby_stations | Find nearby Swiss train stations based on coordinates (latitude, longitude). |
| be_search_connections | Search train connections in Belgium between two stations. Powered by iRail API for real-time routes and schedules. |
| be_search_stations | Search for Belgian train stations by name. |
| be_get_departures | Get live departure board for a Belgian train station. |
| be_get_vehicle | Get details about a specific Belgian train vehicle by its ID. |
| no_search_places | Autocomplete search across stops/addresses/POIs in Norway via Entur Geocoder. |
| no_stop_departures | Upcoming departures for a StopPlace ID (e.g., 'NSR:StopPlace:58368'). |
| no_trip | Door-to-door trip planning between two StopPlaces (NSR IDs). |
| no_nearest_stops | Find nearest StopPlaces for a coordinate (lat, lon) within a radius in meters. |
| uk_live_departures | Get live departure information for a UK train station using its CRS code (e.g., 'PAD' for London Paddington, 'MAN' for Manchester Piccadilly). Uses the TransportAPI station timetables endpoint with live data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |