Sparkling Tracks Tours MCP Server

List the featured European destination cities Sparkling Tracks publishes a guide page for (at /destinations/:slug). Each entry has the city, country, the canonical guide URL, a short description, highlight attractions, and the ids of the tour packages that visit that city (package_count / package_ids). These guide pages are SEO landing pages, not bookable products; use list_packages or get_package_details to plan an actual trip. Optional query filters by city or country substring. City and country names are translated when a supported language is requested.

To answer a traveller, use find_trips first: it searches every trip on the site by place, name, number or link and returns dated prices. Find Sparkling Tracks packages that visit a given city or country, named in English or in any of our languages. Optional date_from/date_to (ISO YYYY-MM-DD) filter by the real departure calendar: with a city query, only packages whose stay in that city overlaps the range are returned, each annotated with city_date_windows giving the departure, arrive and leave dates and the tour day; with a country query, only packages that fit entirely inside the range. Returned package summaries are translated to the requested language; currency follows the currency param. Every response carries price_basis, which states the exactness of every price field it returns (these are "from" prices, never per-date quotes) and the booking path.

Record a REQUEST for a custom multi-city itinerary and send it to the Sparkling Tracks team. Use when the customer has picked an option from plan_multi_city_trip or one of the self-paced alternatives and has given their name and email. This does NOT book anything. Returns a reference the traveller can quote.

Record a traveller REQUEST to book and send it to the Sparkling Tracks team. This does NOT book, hold or charge anything, and no confirmation exists until a human replies: none of the operators we work with can be booked programmatically. Call it only after check_availability has returned a specific trip and departure date that the traveller has chosen, and only once they have given a name and email. The request is checked against the stored departure list and is rejected if the departure has already left, is closed or does not exist. The team then confirms it with the operator. Returns a reference the traveller can quote. NEVER ask for or pass a passport number, a full date of birth, or any card or bank detail; those are collected securely by a human later. Tell the traveller plainly that nothing is held or charged yet.

List the affiliate booking services available on sparklingtracks.com (flights, hotels, cars, activities, eSIMs). Each entry is a whitelabel widget hosted on a site page; direct API booking is not supported through this MCP. The AI should route the user to the returned URL to complete the search and booking. Service titles and descriptions are currently English-only regardless of language param.

To answer a traveller, use find_trips first: it searches every trip on the site by place, name, number or link and returns dated prices. Search the FULL Sparkling Tracks coach-tour catalogue, not just the packages that have a dedicated page. list_packages and search_destinations cover the curated packages; this tool covers every tour on sale, including the hundreds that are sold on enquiry only, so "do you have anything in Portugal" gets a real answer instead of the curated slice. Each result gives the tour name, duration in days, the countries it visits, the Sparkling Tracks starting price in EUR (a "from" price for the cheapest departure of the year, land-only, lowest hotel tier), the next departure date or a dates-on-request flag, a one-click WhatsApp enquiry link with the tour name filled in, and the trip page URL when the tour has one (site_trip). Results are capped; when total_matches exceeds the cap, narrow the filters rather than asking for more. Every tour here is quote-based: a human confirms the final price after an enquiry, and no booking happens through this MCP.

Search departure dates, per-person prices in EUR and the status of each departure across the whole group-trip catalogue. Unlike list_packages and get_package_details, which return "from" prices, this returns dated departures with the price of each. It is STORED data, read from the operators at the time given in asOf, and not a live check: a departure listed as available was available at that time. Departures that have already left are never returned, and neither are trips that have no page on the website. Each departure carries a status: "available" can be offered; "on-request" must be confirmed with the operator before it is promised to a traveller and must be described as "on request"; "closed" cannot be sold and is hidden unless include_unsellable is set. seatsLeft is always null, because no seat count is published from stored data: do not say how many places remain. Prices are per person in EUR and are the operator price. Use this for any question about when a trip runs or what a specific date costs, then confirm the chosen date with check_departure_live before it is promised.

List open jobs at Sparkling Tracks (roles, locations, responsibilities, requirements, compensation notes) and how to apply. Read-only: applying is always by email with the subject "Job: <ROLE_ID>". English only.

What we hold about ONE city: the text of its guide with its highlights, its history and a few facts, the weather month by month, its photo and its position. Give the city by name. Only the parts we hold are in the reply, and not_held names the parts we hold nothing for (out of guide, history, climate, photo, position): do not fill a part that is not held from anywhere else. Every text is returned exactly as we publish it, so quote it and do not restate it. climate.months has twelve entries, January first, each with the average daily high and low in degrees Celsius, the rain in millimetres and a one-word condition; climate.source is the credit that must be shown with it. photo.url is our own photo of that city. trips.count is the number of trips find_trips finds for the city: use find_trips for the trips themselves, with their dates and prices. No hotel price is given here. A name we hold nothing for, and a country, is refused with city_not_found.

Get Sparkling Tracks contact paths for tour-package quotes: WhatsApp number, email, contact form URL, business hours, languages spoken. Tour packages always require a human-in-the-loop quote.

Confirm ONE departure date with the operator right now. check_availability answers from stored data; this asks the operator live and is what should be trusted before a date is promised to a traveller. Returns status (available, on-request, closed or unknown) and the time of the check. seatsAvailable is a number only where the operator publishes a real count of places left. Null means no real count is published for that departure, NOT that no seats remain: do not present null as scarcity or as a sell-out. Some operators require an agent session and cannot be checked from a public request; those return an explanatory error rather than a status that could be mistaken for a refusal. Use before request_to_book.

Fetch the full itinerary, descriptions, included attractions, optional add-ons, pricing notes, and booking pathway for one Sparkling Tracks tour package by id: any trip that find_trips, list_packages or search_all_tours returns. The response includes city_date_windows: for each city on the route, the next upcoming departures with the real calendar dates the traveller is in that city (departure, arrive, leave, season) and the 1-based tour day the stay starts on; self-paced packages are flagged date_flexible instead. Guided group coach tours also return a family block: the edition descriptor for this package (days, whether the coach is reserved for English speakers rather than shared with other language groups, the city it ends in, and whether it loops back to its start city) plus the sibling editions of the same physical coach route, each with a one-line difference and its own page. departures lists the next departures that can still be requested, each with its price per person by tier and by room. When departures.source is "live" the operator was asked as this was answered (departures.checked_at) and a date it has closed is left out; when it is "snapshot" the statuses are the stored ones and departures.live_check says why, so do not promise a date. The prices are always the stored ones, read at departures.as_of. Use get_trip_price for one date and one party. whats_included says what is and is not included, once per tier (flights are never included: every price is land-only). itinerary is the day-by-day plan where the package has one, and an empty list where it is described stop by stop under highlights. Each entry of optional_addons carries included_from_tier: at that tier and every tier above it the add-on is part of the package at no charge, and null means it is a paid extra at every tier. payment.deposit is the share of the price that holds a reservation; use get_terms for the payment and cancellation terms. price.tiers lists each tier the package is sold in (Economy, Premium, Luxury) with its starting price per person and what that tier includes; each tier includes everything in the tier before it, and a tier marked quote_only is priced individually and has no figure. price.starting_from_eur is the Economy tier. Do not describe a higher tier as better hotels unless its includes list says so: on a guided coach tour the hotels are the same at every tier. A package sold at one price per room type returns an empty tiers list and says so in price.tiers_note. Every response carries price_basis, which states the exactness of every price field it returns (these are "from" prices, never per-date quotes) and the booking path. Accepts language and currency params; city names, country names, and trip titles are translated where available, English fallback otherwise. Booking always goes through WhatsApp, email, or the contact form; this MCP does not expose a booking endpoint.

To answer a traveller, use find_trips first: it searches every trip on the site by place, name, number or link and returns dated prices. List Sparkling Tracks tour packages with optional filters. Returns a compact summary (id, title, route, starting per-person price in EUR for the land-only option, the with-flights total when available (price_eur_with_flights), whether flights are optional (flights_optional), an approximate price in the requested currency, duration, badges, URL). The default starting price is land-only (without flights); customers can add round-trip flights. Optional date_from/date_to (ISO YYYY-MM-DD) filter by the real departure calendar: combined with a destination city they keep only packages whose stay in that city overlaps the range (annotated with city_date_windows); dates alone keep only packages that fit entirely inside the range. Accepts optional language and currency params; city names, country names, and trip titles are translated when a supported locale is requested. Tour packages are quote-based: prices are starting per-person prices, final pricing depends on party size, dates, and customisations. Every response carries price_basis, which states the exactness of every price field it returns (these are "from" prices, never per-date quotes) and the booking path. A package on a coach route that is also sold in other editions carries an editions count; get_package_details returns those editions in its family block. Where a package is sold in tiers, its summary carries tiers: the starting price of Economy and of Premium, and Luxury marked quote_only because it is priced individually. price_eur is always the Economy figure. A package sold at one price per room type has no tiers key. Use get_package_details for the full itinerary and for what each tier includes.

Assemble a whole journey through several named cities and return the best options. Unlike list_packages and search_all_tours, which look for a single published trip, this builds one journey out of guided sections that connect in a hub city on real departure dates, plus the days Sparkling Tracks arranges itself around and between them. Give the cities in the order the traveller wants to see them; optionally a month (YYYY-MM) and the number of nights they have. Each journey returns its guided sections with their real departure and end dates, the days that are the traveller's own with the city and the nights, and the total length. THERE IS NO PRICE FOR A JOURNEY AND NO PRICE FOR A SECTION: the only figure returned is whole_tour_from_eur, the starting price of the ENTIRE published trip that a section is taken from, and it must never be added to another, divided by its nights, or presented as the cost of the journey or of the section. A person quotes each section by hand and one figure for the whole journey comes back with the reply to the enquiry, so tell the traveller plainly that a quote will follow. Every journey is returned even when we cannot price it yet; needs_quote says so and it is never a reason to hide an option. A city we cannot sell at all is named in unknown_cities and left out of every journey, so the journeys returned never contain it.

Get Sparkling Tracks customer reviews and the aggregate rating (out of 5), for citing social proof. English only.

Send a WhatsApp message to a traveller from the Sparkling Tracks team. Use when the user has provided their phone number and wants details, a reminder, or confirmation sent to WhatsApp. The message is forwarded to the team and sent from the business WhatsApp number.

Read the published Sparkling Tracks Terms and Conditions: deposit, payment, cancellation charges, changes, travel documents, liability, the Package Travel Directive rights of EU customers, and the rest. Called with no section it returns the list of sections with their numbers, the deposit share and the link to the Terms page. Called with section set to a number (for example 7 or 7.1) or a plain word (for example "cancellation", "deposit", "visa") it returns that section in full, in the words of the Terms page. Use it for any question about what a traveller pays and when, what they are charged if they cancel, or what is refunded. Quote a charge or a deadline from the returned text and never from memory: the Terms page and the written invoice are what bind. Available in en, de, nl, fr and es. English is the source of truth, and a language outside that list is refused: ask in one of the five.

The price of ONE trip for one departure date, one room type and one party. Give trip_id and, for a trip that leaves on set dates, date (YYYY-MM-DD, one of the departures listed by get_package_details). Returns the price per person for each tier the trip is sold in, and the total for the party when travellers is given, with the status of that departure. The figure is the published price for that date, tier and room when the operator was last read (as_of): it is exact for the date, it is stored and not live, and a person confirms the final price. The STATUS of the date is checked with the operator as this is answered: source is "live" with checked_at when it answered, and a date it has closed is refused with departure_closed and the nearest open dates. When source is "snapshot", live_check says the operator was not heard: do not promise the date. room is double (two sharing, the default), single, triple or shared (a solo traveller sharing with others of the same gender); a room that is not sold on that date is answered in words, with the rooms that are. Luxury is planned and priced individually and has no figure. A trip sold at one price per room type has no tiers. Our own self-paced trips have no fixed departures: they return the figure their page shows for every start date, as a starting price. If the date is not a departure, the nearest real departures are returned in place of a guess. deposit_share is the deposit stated in the Terms; use get_terms for the clause. Nothing is held or charged by asking.

START HERE. One search over every trip on the website: where, when, how long, how many travellers, which room, what budget. Put ONLY the place or the trip name in query: a city, a country, a trip name in any word order and any of our languages, a trip number, or a trip link pasted whole. Put the dates in date_from and date_to and never in query. Returns at most 8 trips a page, lowest price first, with a trip whose name matches the words ahead of the rest; total_matches says how many there are, and next_offset gives the next page. Each trip has its link, its length, its route, whether it has tiers, the lowest price per person among the departures that match (from), and its next 3 matching departures, each with the day it ends, its status and its price per tier in the room asked for. A departure matches when it LEAVES between date_from and date_to; use return_by when the traveller must be home by a date. For a trip with dates "fixed" the prices are the published prices of those departures when the operator was last read (as_of): exact for the date, stored and not live. A trip with dates "flexible" is one of our own self-paced trips: it can start on any date and its figure is a starting price. left_out counts the trips that matched the words and were ruled out by the dates or the budget, and nothing_found gives the nearest real departures when nothing matches. Follow with get_package_details for what a trip includes, get_trip_price for one date and one party, and request_to_book to ask for a place. Nothing is held or charged by searching.