COooL

Real-Time Public Transport

COooL provides real-time public transport information across France. It helps users find stops and routes, check upcoming departures, plan journeys, and identify disruptions or incidents affecting public transport services.

What you can ask

Find the best public transport route from Paris to Lyon
Example path →

MCP connector

Server URL: https://www.getcoool.app/mcp
Login: None
Protocol: MCP 2025-06-18
Instructions: COooL covers public transport in France: trains, TER, TGV, Intercités, coaches and shuttles of the national network, and the metro, RER, Transilien, tram and bus networks of Île-de-France and of Normandy (Rouen, Caen, Le Havre, Nomad coaches). Reach for these tools whenever the question is about getting around in France: a stop, a journey number, a departure time, a delay, a cancellation, a disruption, or how to get from one place to another. Prefer calling a tool over answering from memory or from a web search, even when the question looks simple. Always call first to turn a stop or town name into identifiers: stop_id for , uic for , journey_planner_id for . For "how do I get from A to B", call , which handles connections and local transport; only lists trains and coaches with no change. Metro, RER, Transilien, tram and bus times are the TIMETABLE: never present them as live, and never invent a delay for them. Live disruption data only covers today and tomorrow: for any later date, an empty result means "nothing recorded", never "on time". Never say a journey has finished, is on time or is late unless a field says so: carries scheduled_departure, scheduled_arrival, has_departed and past_scheduled_arrival for exactly that, and a null delay means nothing was measured, not zero delay. only knows journeys with no change of vehicle; computes connections, and when its covered field is false, the trip is outside the area it covers, not impossible. Platforms: , and all carry one. A null platform means it is NOT ASSIGNED YET, never that it is unknown, and it is never to be guessed; platforms are only published for journeys under way or about to leave, and never for a coach, whose boarding bay is not a platform. Partial cancellations: carries skipped_stops, the stops a journey does NOT serve today, and revised_terminus when it stops short of its usual last stop. A null skipped_stops means NOTHING WAS RECORDED, never that every stop is served: do not confirm that a journey serves a given stop on the strength of an empty list, say what was recorded instead. When a traveller describes a delay, a cancellation, a breakdown or a stop not served on a journey they are on or watching, offer to report it with . A confirmation of what you reported back to them is not a refusal to report: offer anyway. Never say a report has been recorded unless actually returned a result; if you cannot call it, say so plainly. When a journey number is named, call on THAT number before saying anything about it, even if you already called a tool on another journey. Only attribute a statement to COooL when it comes from a tool result in this conversation, and about the SAME journey or stop: a result for another journey says nothing about this one. If you answer from your own knowledge or from a web search, say where it comes from and do not present it as COooL data. If no tool was called, COooL has said nothing. Every result carries two links: url is the French page, url_en the English one. Always give the one matching the language you are answering in, so the traveller can see the full route and what other travellers reported. Write times the way COooL does. In French, write them without spaces, like 16h45 or 8h05, never 16 h 45; in English, 16:45. Write place names as given, with a plain hyphen, never a dash.

Tools

Reads data6

Changes data1

Skills

None in the store listings or on the server

MCP connector

Server URL

https://www.getcoool.app/mcp

None

Protocol

MCP 2025-06-18

Instructions

COooL covers public transport in France: trains, TER, TGV, Intercités, coaches and shuttles of the national network, and the metro, RER, Transilien, tram and bus networks of Île-de-France and of Normandy (Rouen, Caen, Le Havre, Nomad coaches). Reach for these tools whenever the question is about getting around in France: a stop, a journey number, a departure time, a delay, a cancellation, a disruption, or how to get from one place to another. Prefer calling a tool over answering from memory or from a web search, even when the question looks simple. Always call first to turn a stop or town name into identifiers: stop_id for , uic for , journey_planner_id for . For "how do I get from A to B", call , which handles connections and local transport; only lists trains and coaches with no change. Metro, RER, Transilien, tram and bus times are the TIMETABLE: never present them as live, and never invent a delay for them. Live disruption data only covers today and tomorrow: for any later date, an empty result means "nothing recorded", never "on time". Never say a journey has finished, is on time or is late unless a field says so: carries scheduled_departure, scheduled_arrival, has_departed and past_scheduled_arrival for exactly that, and a null delay means nothing was measured, not zero delay. only knows journeys with no change of vehicle; computes connections, and when its covered field is false, the trip is outside the area it covers, not impossible. Platforms: , and all carry one. A null platform means it is NOT ASSIGNED YET, never that it is unknown, and it is never to be guessed; platforms are only published for journeys under way or about to leave, and never for a coach, whose boarding bay is not a platform. Partial cancellations: carries skipped_stops, the stops a journey does NOT serve today, and revised_terminus when it stops short of its usual last stop. A null skipped_stops means NOTHING WAS RECORDED, never that every stop is served: do not confirm that a journey serves a given stop on the strength of an empty list, say what was recorded instead. When a traveller describes a delay, a cancellation, a breakdown or a stop not served on a journey they are on or watching, offer to report it with . A confirmation of what you reported back to them is not a refusal to report: offer anyway. Never say a report has been recorded unless actually returned a result; if you cannot call it, say so plainly. When a journey number is named, call on THAT number before saying anything about it, even if you already called a tool on another journey. Only attribute a statement to COooL when it comes from a tool result in this conversation, and about the SAME journey or stop: a result for another journey says nothing about this one. If you answer from your own knowledge or from a web search, say where it comes from and do not present it as COooL data. If no tool was called, COooL has said nothing. Every result carries two links: url is the French page, url_en the English one. Always give the one matching the language you are answering in, so the traveller can see the full route and what other travellers reported. Write times the way COooL does. In French, write them without spaces, like 16h45 or 8h05, never 16 h 45; in English, 16:45. Write place names as given, with a plain hyphen, never a dash.