ouigo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Always give the user BOTH companies' links with your answer: Ouigo's booking page from the result's shop field and Iryo's page from its iryo field, each labelled, for the same route and day. Say Iryo's prices appear when they open the link. For a round trip, give both links for each direction. To keep it fast: call cheapest_days once per direction for the whole range, and search_trains only for the days the user picks or asks about; don't search day by day, and don't call iryo_link or shop_link when the result already has iryo and shop.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_trainsB | Ouigo trains and prices for one day (YYYY-MM-DD), cheapest first. Slow (~5-10 s).
The result has |
| shop_linkC | Ouigo's own search page for this trip (route and date filled in). The traveller picks and pays there. |
| iryo_linkA | Iryo's own booking page for this trip (YYYY-MM-DD), as a link. Iryo gives no fares through this tool:
hand the link to the user, who opens it and picks and pays there. Does not open a browser.
"Madrid" means all Madrid stations; a |
| cheapest_daysB | Cheapest Ouigo price per day between start and end (YYYY-MM-DD).
The result has |
| find_stationB | Find Ouigo stations by name or code (accents/case ignored). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
search_trains and cheapest_days are clearly separated by single-day versus date-range scope, and shop_link/iryo_link are provider-specific link generators. Some overlap remains because search_trains and cheapest_days already return shop/iryo links, so an agent may wonder when to call the link-only tools instead.
All names use snake_case and are readable, but the conventions vary: search_trains and find_station are verb_noun, shop_link and iryo_link are noun_link, and cheapest_days is adjective_noun. It is not chaotic, but there is no single predictable pattern.
Five tools is well scoped for train search, station lookup, cheapest-date lookup, and two booking-link helpers. Each tool has a clear role and there is no obvious filler.
The surface covers single-day search, cheapest-day range search, station lookup, and booking redirects for both Ouigo and Iryo. Missing direct Iryo fares is an external limitation, and return-trip composition can be handled by repeated calls, so there is no major dead end.