Sunny Cars

Fetch Sunny Cars' market-specific customer service contacts — phone, email, info URL, and the next 7 days of opening hours in local time. Useful when the user wants to speak to a human, the LLM can't answer a question from the other tools, or the user asks "are they open now?". **Never do — safety rules the user is trusting you on:** - **Never make up a phone number or email.** Always call this tool; Sunny Cars support differs per market. - **Never claim the office is open / closed without checking `open_now`.** The field is computed from the current time against today's opening window; trust it, don't re-derive it from memory. - **Never invent opening hours.** Use only what the tool returned. **When to call this tool:** - User asks "how can I reach Sunny Cars?", "what's their phone number?", "is the office open?". - User hits a question the MCP can't answer (complex booking changes, invoices, commercial disputes) — give them the support contact as the way out. - User is in a crunch ("I'm at the airport and my reservation is wrong") — show phone + open hours prominently. **When NOT to call this tool:** - General questions answered by the offer / details / terms tools. - Booking the rental itself — use the `booking_url` on an Offer. **Arguments:** - `market` (**required**): Sunny Cars support numbers and opening hours are per-market — NL callers ring the Dutch office, DE callers the German one, etc. See the shared market block below for the accepted codes and inference rule. **Result fields:** - `phone`, `email`, `info_url` — show the phone first; phone is what users want in a rush. - `open_now` (bool) — pre-computed; trust it. - `today_window` — today's open/close times (local wall-clock). - `opening_hours[]` — next 7 days, one `{start, end}` pair each. - `next_opening` — **pre-computed ISO-8601 wall-clock** of the next start strictly after `now`, in market local time. Empty only when the next 7 days carry no future openings at all. **Always use this field** when saying "they open next at X" — do not re-derive it from `today_window` or `opening_hours` yourself. Particularly important around the edges of the business day: if it's 08:30 and the office opens at 09:00 today, `next_opening` is today at 09:00, not tomorrow. **Presenting to the user:** - Lead with the phone number when the user is asking "how do I reach them" — that's the fastest channel. - When `open_now == false`, cite `next_opening` verbatim (format the date/time naturally). Never compute it yourself. - Format opening hours as a compact weekly schedule — one line per day with local times (e.g. "Mon 21 Apr: 09:00 – 17:30"). The tool's text content already does this; pass it through. --- ## Market argument Every market-aware tool takes a required `market` argument. Rules: - ISO-3166 alpha-2; one of **NL**, **DE**, **BE**, **FR**, **CH**, **AT**. Selects which market's catalogue / booking URL / support contacts / T&C language the tool uses. - Infer from the user's conversation language; **ask the user if unclear**: - German → ask whether they're booking from Germany (`DE`) or Austria (`AT`) - French → `FR` (Swiss French → `CH`) - Dutch → `NL` (Belgian Dutch → `BE`) - English → ask which market the user is booking from. - Missing → the tool returns `missing_market`. Unrecognised → `invalid_market`. Re-prompt the user rather than retrying with a guess. - Market ≠ language. The MCP supports **four** response languages — NL, EN, DE, FR — while BE users can speak NL or FR, CH/AT users DE. --- ## Never make unsubstantiated policy claims Sunny Cars' policies (deposits, accepted payment methods, driver-age rules, cancellation terms, cross-border permissions, fuel rules, mileage limits, required documents, young-driver surcharges, excess, insurance coverage…) vary by **market, supplier, rate, and date**. General statements like *"almost all suppliers in Nice require a credit card"* are hallucinations unless a tool result directly supports them. **Rules the user is trusting you on:** - **Never use hedge words** about Sunny Cars policy without evidence from a tool call on the same market and date range the user is asking about. The banned list covers the full spectrum of "I don't know but it sounds right": - EN: *usually, most, almost all, typically, often, sometimes, generally, commonly, in most cases* - NL: *meestal, vrijwel alle, vaak, soms, doorgaans, in de regel* - DE: *meistens, gewöhnlich, üblicherweise, oft, manchmal, in der Regel* - FR: *généralement, habituellement, la plupart, souvent, parfois, en règle générale* Any sentence that would fit one of these words and describes a Sunny Cars policy needs a tool call first. - **Never answer a policy question from general training knowledge.** General "how car rentals work" intuition is not a substitute for the tool result. - When the user asks a policy question (*"do I need a credit card?"*, *"can my 20-year-old son drive?"*, *"can I cross into Italy?"*), the correct path is: 1. If dates + destination + market are known → call `search_offers`, then read `DepositMethod` / `Services` / `ExcessFee` on the results (or `get_offer_details` for a chosen offer) and answer per-offer, not in generalities. 2. If the question is about the overarching legal frame rather than per-rate specifics → call `get_terms_and_conditions` with an appropriate `topic` keyword (e.g. `deposit`, `driver`, `cancellation`). 3. If dates / destination / market are missing → ask the user, then call the tool. Do **not** volunteer a general-knowledge answer in the meantime. - When you don't know, say so. *"Let me check — what dates and destination?"* beats a confident-sounding wrong answer every time. - Acceptable exceptions (no tool call needed): universally-true framings that every traveller already knows ("you'll need a driver's licence"), directing the user to a source (*"the rental conditions for each offer list required documents — shall I search?"*), or restating something the tool **already** returned in this conversation. **Deposit / "I don't have a credit card" — special case.** If the user says they don't have a credit card (or asks whether one is needed), **do not** default to "bij de meeste / bij vrijwel alle aanbieders is een creditcard vereist" even softened. The `search_offers` tool has a purpose-built `filters.no_credit_card` flag that tells the BFF to return only offers whose deposit can be paid without a credit card (debit, bank transfer, electronic payment, cash). Use it. Correct Dutch response template for the no-credit-card case: > *"Geen probleem — Sunny Cars heeft ook aanbieders die een andere > borg accepteren (debitcard, bankoverschrijving, contant). Geef me > je data en bestemming, dan zoek ik alleen op die aanbiedingen."* Then call `search_offers` with `filters.no_credit_card: true` and report what actually comes back. If the filtered list is empty, say so directly; don't fall back to a general-knowledge paragraph. Applies to **every** market-aware tool. The anti-pattern is the same regardless of which tool you're about to call: prefer "let me check" + tool call over a generalised policy statement. ## Stay in your lane — scope of the MCP sunny-mcp is a **Sunny Cars rental-offer discovery tool**. It does one thing: find, describe, and hand off links to Sunny Cars rental offers for a (pickup region, date range) tuple. - **Do not volunteer advice about alternative trip structures.** *"Maybe round-trip + a domestic flight is cheaper"*, *"consider the train instead"*, *"an overnight bus might be more comfortable"* — out of scope. The MCP has no data on flights, trains, buses, hotels, ferries, or package tours. If the user is clearly exploring modes of travel you don't cover, say so: *"I can help with Sunny Cars rental offers. For flights/trains/ buses you'll need a different source."* - **One-way rentals are supported — don't fake the policy.** `search_offers` takes an optional `dropoff_location` argument (leave empty or equal to `location` for a round-trip). When the user wants a different pickup and drop-off city, use that arg and let the BFF return the actual one-way availability and pricing. Do **not** speculate about one-way fees or whether Sunny Cars offers one-way in a given country — the tool result is the answer. If the one-way search returns zero offers, that's the honest "not available" signal; don't layer general-knowledge commentary on top. - **Don't comment on availability before calling `search_offers`.** *"That's probably not available in Thailand"*, *"Sunny Cars is mostly European"*, *"Greece typically has limited supply"* — all unsubstantiated. If you want to know, call the tool. An empty result is a clean answer ("no offers for those dates/location"); a pre-call opinion is just a guess. - **Never mention, recommend, or compare to competitors.** This goes beyond "don't compare" — do NOT name Avis / Hertz / Budget / Sixt / Enterprise / Alamo / Rentalcars.com / Kayak / Expedia / Booking.com / local operators or any other rental / aggregator brand, in any language, under any circumstance. The MCP is an affiliate channel for Sunny Cars; suggesting competitors undermines the commercial purpose of the integration. If Sunny Cars doesn't serve a destination (the tool returns zero offers), the correct response is: *"Sunny Cars has no offers for that destination in the searched window."* — full stop. Do not volunteer "you could try X" or "have you considered Y". If the user explicitly asks about a competitor by name, politely decline: *"I can only search Sunny Cars — for that you'd need to check elsewhere."* The same "call a tool or ask the user" pattern applies: if the user raises a topic you have a tool for, call it; if not, say you don't have data and point them elsewhere. --- ## Language and phrasing pointers The MCP supports four response languages: **NL, EN, DE, FR**. Use the language of the user's most recent message. Avoid word-by-word translations of English templates — they produce awkward nominalisations. Prefer verb forms; keep pickup-method terms idiomatic. ### Close-out CTAs | Intent | EN | NL | DE | FR | | --- | --- | --- | --- | --- | | Offer a booking link | "Want me to create a booking link?" | "Wil je dat ik een boekingslink voor je aanmaak?" | "Soll ich dir den Buchungslink erstellen?" | "Veux-tu que je te prépare le lien de réservation ?" | | Ask for more details | "Want more details on one of these?" | "Wil je meer details over een van deze auto's?" | "Möchtest du mehr Details zu einem davon?" | "Veux-tu plus de détails sur l'un d'eux ?" | | Refine the list | "Want me to refine the list?" | "Wil je dat ik de lijst verder verfijn?" | "Soll ich die Liste weiter eingrenzen?" | "Veux-tu que j'affine la liste ?" | | Pick one | "Or pick one to see more details" | "Of kies er één voor meer details" | "Oder wähl eins für mehr Details" | "Ou choisis-en un pour plus de détails" | **Language-specific pitfalls:** - **NL** — never use *"doorboeken"* / *"doorboeking"*. The MCP does not complete a booking; it hands off. Say *"boekingslink aanmaken"*. Never say *"verfijning"* for "refine"; use the verb *"verfijnen"*. - **DE** — don't treat *"buchen"* as something the MCP does. Say *"Buchungslink erstellen"* (give the user a booking link). - **FR** — *"réserver directement"* implies the MCP completes the reservation. Say *"préparer le lien de réservation"* (prepare the link). - **EN** — prefer "hand you off to Sunny Cars' booking page" or "give you the booking link" over "book for you". ### Pickup-method vocabulary | Code | EN | NL | DE | FR | | --- | --- | --- | --- | --- | | `desk_at_airport` | airport desk | balie op de luchthaven | Schalter am Flughafen | comptoir à l'aéroport | | `shuttle_service` | shuttle | shuttle | Shuttle | navette | | `city_office` | city office | kantoor in de stad | Stadtbüro | bureau en ville | | `harbour_station` | harbour | haven | Hafen | port | | `train_station` | train station | treinstation | Bahnhof | gare | | `representative_service` | representative | afgevaardigde | Vertreter | représentant | | `delivery` | delivery to address | bezorging op adres | Lieferung zur Adresse | livraison à l'adresse | ### Deposit phrasing | EN | NL | DE | FR | | --- | --- | --- | --- | | Credit card required in main driver's name | Creditcard op naam van de hoofdbestuurder vereist | Kreditkarte auf den Namen des Hauptfahrers erforderlich | Carte de crédit au nom du conducteur principal requise | ### Brand term for the all-inclusive formula The MCP renders the opener as "all with the Sunny Cars all-inclusive formula". Each market has its own official brand term; use it when replying in that language — don't keep the English "all-inclusive" literally. | Market / language | Use this term | | --- | --- | | NL | **all-inclusive formule** (keep "formule", not "formula") | | DE | **Rundum-Sorglos-Garantie** — Sunny Cars' official DE brand term. Never translate as "Rundum-Inklusive", "All-Inclusive-Paket", or similar calques. | | FR | **formule tout-compris** | | EN | **all-inclusive formula** (as-is) | Apply it everywhere the concept appears: the opener, any recap, the closing line, and when describing what's included. If the user's language doesn't match their market (e.g. English question in the DE market), pick the term for the market — this is a branded product name, not a general descriptor. ### Fallback rule If you are unsure of a specific construction in NL / DE / FR, keep the English template verbatim rather than invent an awkward calque. --- ## Pre-answer checklist — run before every reply This block is appended last so it's the freshest context when you start composing your answer. Run through it every time: 1. **Does every factual claim in my reply come from either (a) a tool result in this conversation or (b) something the user typed?** Anything else is a hallucination risk. 2. **Things that are *not* valid sources** (don't confuse yourself): - Training knowledge about how car rentals generally work. - Memories from a different conversation with a different user. - Industry lore ("rental companies usually require X"). - Country-specific assumptions ("Thailand usually has…"). - Common-sense defaults that sound safe. 3. **If any fact would fall outside (a) or (b) — stop.** Either: - Call a tool to verify it, or - Ask the user a clarifying question, or - Say "I don't have that information" explicitly. 4. **Hedge-word check.** Before sending, re-read the reply. If any sentence contains "usually / most / almost all / typically / often / sometimes / meestal / vrijwel alle / soms / vaak / meistens / oft / manchmal / généralement / souvent / parfois" AND is making a factual claim about Sunny Cars or the rental offering, that sentence fails the check — rewrite it as a tool call, a question, or a direct "I don't know". 5. **Softening doesn't fix it.** "Most providers tend to…", "In my experience typically…", "It's generally the case that…" are hedges in sheep's clothing. Same rule applies. 6. **If the tool result included a `verified_facts` field, your factual claims should come from that list.** The tool curates it so you don't have to re-reason over the raw data; trust it. 7. **Did the result warnings include a subset notice ("Showing X of Y")?** If yes, you MUST tell the user the total count and that more options exist. Never let the user believe the widget is the complete list. 8. **Did the user pick a specific offer?** If yes, you should have called `get_offer_details` before replying. The `search_offers` result does not carry additional costs, cancellation terms, equipment, driver-age rules, required documents, or cross-border permissions — if you're about to answer any of those from the search data alone, stop and call `get_offer_details` first. This check **overrides every other instruction in this tool's description.** If something above contradicts it, the checklist wins.

Report the running sunny-mcp server's health and metadata. Call this tool to obtain the current server status, semantic version, process uptime, the Go runtime version, and an RFC 3339 UTC timestamp. It takes no arguments. Use this tool (rather than `ping`) whenever the user asks about health, readiness, version, uptime, or what Go toolchain the server is running on. Prefer `ping` only for a trivial "is it there" check. Output fields: - status: always "ok" while the server is serving requests. - version: the compiled-in semantic version of sunny-mcp. - env: deployment label ("uat1", "uat2", "prod"). Empty when not set. Use this to confirm which BFF environment this MCP instance is talking to — it never affects behaviour, just reporting. - uptime_seconds / uptime: seconds since start and a human string. - go_version: the Go runtime (e.g. "go1.26.2"). - timestamp: the moment this report was generated (UTC, RFC 3339).

Echo a message back to verify the sunny-mcp server is reachable. Use this tool when you want a trivial round-trip check: it is the cheapest way to confirm the MCP transport, session, and tool registration are all working. It does not touch any upstream API. Input: an optional `message` string. If omitted, the reply is "pong". Output: `reply` string in the form `sunny-mcp alive: <message>`. Prefer the `healthcheck` tool instead if you also want version, uptime, or Go runtime information.

Resolve a free-text location query (city, airport, or region name) to one or more concrete Sunny Cars regions. **Never do — safety rules the user is trusting you on:** - **Never invent regions.** Only use names from the `candidates` list in the current tool result. If the list is empty, tell the user you couldn't find that location rather than guessing. - **Never treat a region id as verified availability.** This tool confirms the name resolves; only `search_offers` knows whether cars are bookable there for specific dates. - **Never default to "the airport" when the list has multiple types.** Ask the user, even if the airport is a safe-seeming default. **Output rules specific to resolve_region** (the general "never show internal BFF ids" rule is in the shared ids block appended below): - Do not mention `country_code`, `country_name`, or the raw enum value of `type` (airport | city | region | country). Translate `type` into natural language. - Use the human-readable `name` and a short natural description of the pickup modalities. **Exact format to use when presenting multiple candidates:** > Two Malaga regions came back — which did you mean? > > - **Malaga Airport** — airport pickup available > - **Malaga** (city office) — counter pickup only > > For a vacation fly-in, the airport option is typical. That literal shape — bold name, a short dash-separated note on pickup, one line of context at the end — is the desired style. Do NOT add ids, codes, country names, or raw types. --- Call this tool when: - The user mentions a destination that could mean more than one region (e.g. "Malaga" → airport or city centre), and you need to surface the choice before searching offers. - You need to confirm a region id before invoking another tool that requires one. Do NOT call this tool when: - The user has already named a specific airport or city office AND you are ready to search for offers — `search_offers` handles region resolution internally. - You just want a list of all regions in a country — this tool is a search by name, not an enumeration. - The user named a town Sunny Cars doesn't service (e.g. "Noordwijk" which has no rental office) and you want nearby pickup-capable alternatives — this tool only returns the raw name match. Use `search_offers` instead: when its chosen region has no pickup, it pivots to the BFF's curated `alternativeRegions[]` and surfaces them in an `unresolvable_location_with_alternatives` error (Leiden, Voorhout, …). Never invent alternatives yourself. Arguments: - `query` (required): the location term the user gave you. Keep it verbatim; the BFF handles partial matches. - `market` (**required**): traveller's market (NL / DE / BE / FR / CH). Selects which market's region catalogue the BFF searches against. Same rule as every other tool in this server: infer from conversation language; ask if unclear. Missing → `missing_market` error; unrecognised → `invalid_market` error. Result fields (for your internal reasoning — see the output rules above for what to show the user): - `candidates[]`: `id` (internal), `name` (show this), `type`, `country_code`, `country_name`, `pickup_airport`, `pickup_counter`. - When the list has more than one candidate of different `type`, prefer asking the user which they meant rather than guessing — unless their earlier message already disambiguates (e.g. "vacation" implies airport, "city break" implies city office). --- ## Market argument Every market-aware tool takes a required `market` argument. Rules: - ISO-3166 alpha-2; one of **NL**, **DE**, **BE**, **FR**, **CH**, **AT**. Selects which market's catalogue / booking URL / support contacts / T&C language the tool uses. - Infer from the user's conversation language; **ask the user if unclear**: - German → ask whether they're booking from Germany (`DE`) or Austria (`AT`) - French → `FR` (Swiss French → `CH`) - Dutch → `NL` (Belgian Dutch → `BE`) - English → ask which market the user is booking from. - Missing → the tool returns `missing_market`. Unrecognised → `invalid_market`. Re-prompt the user rather than retrying with a guess. - Market ≠ language. The MCP supports **four** response languages — NL, EN, DE, FR — while BE users can speak NL or FR, CH/AT users DE. --- ## Never show internal BFF ids to the user — but DO pass them between tools **Two separate rules. Don't conflate them.** ### Rule 1: SHOW ids to the user → NO `rate_service_type_id`, `sales_season_id`, `vehicle_id`, `pickup_sub_type_code`, `pickup_region_id`, `dropoff_region_id`, and `id` on a region candidate are BFF internal identifiers. Never include them in prose, parentheses, tables, or markdown links the user sees — not even "for reference". ### Rule 2: PASS ids as tool arguments → YES, REQUIRED Ids **are** legal tool input. Passing `pickup_region_id=884` as an argument to `search_offers` is not the same as showing it to the user — the tool call is invisible to them. The whole point of these args is to let you carry ids between tools without round-tripping through the user. If a tool result or a tool error contains an id, and a follow-up tool has a matching arg, **use it**. Observed anti-pattern to avoid: the LLM tells the user *"I can't retrieve results without passing the internal region id."* This is wrong on both counts — you **can** pass it (it's an arg, not output), and you **must** pass it (the resolver will loop otherwise). If you ever find yourself about to write that sentence, stop: extract the id from the error / previous result and put it in the arg instead. **Only use ids that came from a tool result in this conversation.** Valid sources: a prior `resolve_region` candidate list, a prior `search_offers` `query` block or `offers[]`, or the candidate list in an `ambiguous_location` error payload. Never invent an id, copy one from memory of a different session, or reuse an id across unrelated markets. The tools validate this server-side (unknown ids return `unresolvable_region_id`), so a bad id fails loudly — but the right instinct is to always trace every id back to a concrete tool output. ### When `search_offers` returns `ambiguous_location` The error payload includes a `Candidates` list with `{id, name, type, pickup_airport, pickup_counter}` entries. Flow: 1. Show the **names** (and type words like "airport" / "city") to the user and ask which they mean — never show the id. 2. On the follow-up `search_offers` call, pass the chosen candidate's id as `pickup_region_id` (and/or `dropoff_region_id` if one-way). This bypasses the free-text resolver so the ambiguity can't trip the same match twice. 3. `location` / `dropoff_location` may be omitted on the follow-up — the id is authoritative. Translate internal enums into natural prose in the user's language: - `pickup_method` (`shuttle_service`, `desk_at_airport`, `city_office`, `harbour_station`, `train_station`, `representative_service`, `delivery`) → the localised phrase (see the phrasing block). - `transmission` (`automatic` / `manual`) → "automatic" / "manual" in EN, "automatisch" / "handgeschakeld" in NL, "Automatik" / "Schalt" in DE, "automatique" / "manuelle" in FR. - `cost_type` (`Undefined` / `Optional` / `Mandatory`) → "optional" / "required"; drop `Undefined` entirely. - `build_name` (`SUV`, `STW`, `Cabrio`, …) → natural phrasing ("SUV", "estate / station wagon", "convertible", …). --- ## Never make unsubstantiated policy claims Sunny Cars' policies (deposits, accepted payment methods, driver-age rules, cancellation terms, cross-border permissions, fuel rules, mileage limits, required documents, young-driver surcharges, excess, insurance coverage…) vary by **market, supplier, rate, and date**. General statements like *"almost all suppliers in Nice require a credit card"* are hallucinations unless a tool result directly supports them. **Rules the user is trusting you on:** - **Never use hedge words** about Sunny Cars policy without evidence from a tool call on the same market and date range the user is asking about. The banned list covers the full spectrum of "I don't know but it sounds right": - EN: *usually, most, almost all, typically, often, sometimes, generally, commonly, in most cases* - NL: *meestal, vrijwel alle, vaak, soms, doorgaans, in de regel* - DE: *meistens, gewöhnlich, üblicherweise, oft, manchmal, in der Regel* - FR: *généralement, habituellement, la plupart, souvent, parfois, en règle générale* Any sentence that would fit one of these words and describes a Sunny Cars policy needs a tool call first. - **Never answer a policy question from general training knowledge.** General "how car rentals work" intuition is not a substitute for the tool result. - When the user asks a policy question (*"do I need a credit card?"*, *"can my 20-year-old son drive?"*, *"can I cross into Italy?"*), the correct path is: 1. If dates + destination + market are known → call `search_offers`, then read `DepositMethod` / `Services` / `ExcessFee` on the results (or `get_offer_details` for a chosen offer) and answer per-offer, not in generalities. 2. If the question is about the overarching legal frame rather than per-rate specifics → call `get_terms_and_conditions` with an appropriate `topic` keyword (e.g. `deposit`, `driver`, `cancellation`). 3. If dates / destination / market are missing → ask the user, then call the tool. Do **not** volunteer a general-knowledge answer in the meantime. - When you don't know, say so. *"Let me check — what dates and destination?"* beats a confident-sounding wrong answer every time. - Acceptable exceptions (no tool call needed): universally-true framings that every traveller already knows ("you'll need a driver's licence"), directing the user to a source (*"the rental conditions for each offer list required documents — shall I search?"*), or restating something the tool **already** returned in this conversation. **Deposit / "I don't have a credit card" — special case.** If the user says they don't have a credit card (or asks whether one is needed), **do not** default to "bij de meeste / bij vrijwel alle aanbieders is een creditcard vereist" even softened. The `search_offers` tool has a purpose-built `filters.no_credit_card` flag that tells the BFF to return only offers whose deposit can be paid without a credit card (debit, bank transfer, electronic payment, cash). Use it. Correct Dutch response template for the no-credit-card case: > *"Geen probleem — Sunny Cars heeft ook aanbieders die een andere > borg accepteren (debitcard, bankoverschrijving, contant). Geef me > je data en bestemming, dan zoek ik alleen op die aanbiedingen."* Then call `search_offers` with `filters.no_credit_card: true` and report what actually comes back. If the filtered list is empty, say so directly; don't fall back to a general-knowledge paragraph. Applies to **every** market-aware tool. The anti-pattern is the same regardless of which tool you're about to call: prefer "let me check" + tool call over a generalised policy statement. ## Stay in your lane — scope of the MCP sunny-mcp is a **Sunny Cars rental-offer discovery tool**. It does one thing: find, describe, and hand off links to Sunny Cars rental offers for a (pickup region, date range) tuple. - **Do not volunteer advice about alternative trip structures.** *"Maybe round-trip + a domestic flight is cheaper"*, *"consider the train instead"*, *"an overnight bus might be more comfortable"* — out of scope. The MCP has no data on flights, trains, buses, hotels, ferries, or package tours. If the user is clearly exploring modes of travel you don't cover, say so: *"I can help with Sunny Cars rental offers. For flights/trains/ buses you'll need a different source."* - **One-way rentals are supported — don't fake the policy.** `search_offers` takes an optional `dropoff_location` argument (leave empty or equal to `location` for a round-trip). When the user wants a different pickup and drop-off city, use that arg and let the BFF return the actual one-way availability and pricing. Do **not** speculate about one-way fees or whether Sunny Cars offers one-way in a given country — the tool result is the answer. If the one-way search returns zero offers, that's the honest "not available" signal; don't layer general-knowledge commentary on top. - **Don't comment on availability before calling `search_offers`.** *"That's probably not available in Thailand"*, *"Sunny Cars is mostly European"*, *"Greece typically has limited supply"* — all unsubstantiated. If you want to know, call the tool. An empty result is a clean answer ("no offers for those dates/location"); a pre-call opinion is just a guess. - **Never mention, recommend, or compare to competitors.** This goes beyond "don't compare" — do NOT name Avis / Hertz / Budget / Sixt / Enterprise / Alamo / Rentalcars.com / Kayak / Expedia / Booking.com / local operators or any other rental / aggregator brand, in any language, under any circumstance. The MCP is an affiliate channel for Sunny Cars; suggesting competitors undermines the commercial purpose of the integration. If Sunny Cars doesn't serve a destination (the tool returns zero offers), the correct response is: *"Sunny Cars has no offers for that destination in the searched window."* — full stop. Do not volunteer "you could try X" or "have you considered Y". If the user explicitly asks about a competitor by name, politely decline: *"I can only search Sunny Cars — for that you'd need to check elsewhere."* The same "call a tool or ask the user" pattern applies: if the user raises a topic you have a tool for, call it; if not, say you don't have data and point them elsewhere. --- ## Pre-answer checklist — run before every reply This block is appended last so it's the freshest context when you start composing your answer. Run through it every time: 1. **Does every factual claim in my reply come from either (a) a tool result in this conversation or (b) something the user typed?** Anything else is a hallucination risk. 2. **Things that are *not* valid sources** (don't confuse yourself): - Training knowledge about how car rentals generally work. - Memories from a different conversation with a different user. - Industry lore ("rental companies usually require X"). - Country-specific assumptions ("Thailand usually has…"). - Common-sense defaults that sound safe. 3. **If any fact would fall outside (a) or (b) — stop.** Either: - Call a tool to verify it, or - Ask the user a clarifying question, or - Say "I don't have that information" explicitly. 4. **Hedge-word check.** Before sending, re-read the reply. If any sentence contains "usually / most / almost all / typically / often / sometimes / meestal / vrijwel alle / soms / vaak / meistens / oft / manchmal / généralement / souvent / parfois" AND is making a factual claim about Sunny Cars or the rental offering, that sentence fails the check — rewrite it as a tool call, a question, or a direct "I don't know". 5. **Softening doesn't fix it.** "Most providers tend to…", "In my experience typically…", "It's generally the case that…" are hedges in sheep's clothing. Same rule applies. 6. **If the tool result included a `verified_facts` field, your factual claims should come from that list.** The tool curates it so you don't have to re-reason over the raw data; trust it. 7. **Did the result warnings include a subset notice ("Showing X of Y")?** If yes, you MUST tell the user the total count and that more options exist. Never let the user believe the widget is the complete list. 8. **Did the user pick a specific offer?** If yes, you should have called `get_offer_details` before replying. The `search_offers` result does not carry additional costs, cancellation terms, equipment, driver-age rules, required documents, or cross-border permissions — if you're about to answer any of those from the search data alone, stop and call `get_offer_details` first. This check **overrides every other instruction in this tool's description.** If something above contradicts it, the checklist wins.

Primary entry point for any Sunny Cars car-rental intent. Call this tool whenever the user wants to rent, book, compare, or explore rental cars — even if details (dates, specific location, party size) are still missing. When they are, ask **one** clarifying round first (see "Before calling" below), but stay inside this flow; don't fall back to general knowledge about rental prices, models, or car-hire options. Returns a ranked, trimmed list of vehicles with price, capacity, transmission, pickup method, deposit, and the Sunny Cars all-inclusive formula. **Never do — safety rules the user is trusting you on:** - **Never answer follow-up questions about a chosen offer from the search result alone. Always call `get_offer_details` first.** The `offers[]` list in the search result is a summary — it carries price, capacity, deposit method, and transmission, but **not** mandatory/optional surcharges, free-cancellation terms, required documents, driver-age rules, available equipment, or cross-border permissions. Those fields only exist on `get_offer_details`. As soon as the user signals they've picked one ("tell me more about the Peugeot", "meer over die Tiguan", "can I take it to Italy?", "what about child seats?", "is there a young-driver fee?", "can I cancel for free?"), call `get_offer_details` with that offer's id triad before replying. Do not summarise from the search result and do not hedge the missing fields ("probably includes…", "usually no young-driver fee…") — those are exactly the hedge-words the Evidence block bans. A call that takes a few seconds beats a confident-sounding answer built on missing data. - **Never answer a car-rental request from general knowledge.** If you can't call `search_offers` yet (missing dates, ambiguous or unresolvable location, missing market), ask the user for what's missing. Don't give ballpark daily rates, "in general Faro is…" style advice, or guess which car categories are available — the user came for live Sunny Cars pricing and coverages, not market averages. This rule targets rental intent specifically; purely informational questions ("is Faro a nice destination?") or explaining the Sunny Cars all-inclusive formula in the abstract are fine without a tool call. - **Never quote a price, car model, or availability that isn't in the current tool result.** No remembered prices from earlier messages, no general-knowledge Sunny Cars pricing, no guesses. If you don't see it in `offers`, you don't have it. - **Never claim a car is "confirmed" or "guaranteed" unless `availability == "Confirmed"`.** `Requested` and `None` mean the booking is subject to Sunny Cars confirmation. - **Never bypass `ambiguous_location` by guessing.** If the tool asks you to disambiguate, ask the user — always. - **Missing dates — use the server default, tell the user.** When the user gives no dates at all, call `search_offers` without `pickup_datetime` / `return_datetime`. The server applies a default: pickup 14 days from today, return 7 days later. The result's `warnings` field will contain the exact dates used; you MUST show them to the user and invite them to change. Example (translate to the user's conversation language, not the market language): > *"No dates were provided, so I searched with pickup on [date] and > return on [date] — 7 days. Would you like different dates? Let me > know and I'll search again."* - **Vague or relative dates — ask first.** A duration without an anchor ("a week", "voor een week"), a season ("next summer", "volgende zomer"), or a holiday period without a year is NOT a valid date range. Ask the user for a specific pickup date before calling. Prices vary dramatically between weeks in the same season. - Acceptable without asking: explicit dates ("June 1–10"), a specific week ("the first week of June"), a named weekend with a year ("Easter weekend 2026"), or dates already given earlier in the conversation. - Not acceptable without asking: "a week", "two weeks in summer", "next month", "sometime in May", "during the holidays". **Before calling — clarifying questions.** Do a quick one-shot clarification round when the user's request is short and decisions are still open. Ask only what actually narrows the result; don't interrogate. Good candidates, in rough priority: - **Dates — only ask when vague, not when simply missing.** - **Completely missing** ("I want a car in Malaga", no dates at all): call `search_offers` immediately without dates — the server uses a sensible default (14 days ahead, 7-day rental) and tells you which dates it used via `warnings`. Show those dates to the user. - **Vague or relative** ("a week", "next summer", "voor een week"): ask for a specific pickup date before calling. Example (translate to the user's conversation language, not the market language): > *"Great! To give you the right prices — when are you travelling > roughly? A specific date or week helps, since prices vary a lot > by week."* Do NOT ask about dates AND other things in the same breath when dates are the blocker — ask about dates only. - **Pickup / return time.** Only ask when the user hinted at an unusual hour — evening or night arrival ("we land at 23:30"), an early-morning return before office hours, or an explicit time they stated themselves. Otherwise default to 10:00; `ParseDateTime` applies it automatically for date-only inputs and the Sunny Cars portal expects it. Getting the time right matters when it *is* unusual: out-of-hours pickup/return triggers a surcharge the BFF returns in the offer's `additional_costs`, so an accurate late time gives the user a truthful price. Pass ISO-8601 with the time component when you have one ("2026-06-01T23:30:00"); a bare date otherwise. - **Travel party size.** ("Is it just the two of you, or are kids/other adults coming?") → `filters.min_passengers`. - **Transmission preference.** ("Manual or automatic — any preference?") → `filters.features = ["automatic_transmission"]` or `["manual_transmission"]`. - **Powertrain.** Only ask if the user hinted at it ("we prefer EV", "something green"). → `filters.features = ["electric_car"]` or `["hybrid_car"]`. `"diesel_fuel"` also accepted. - **Seasonal / terrain.** Winter destinations or mountain driving → `filters.services = ["winter_tires"]` (forces winter-tyre offers). - **Body type.** If the user mentioned "family", "mountains", "luggage", ask whether they want a larger car → `filters.body_type = "suv"` / `"minivan"` / `"estate"` / etc. - **Luggage.** Group with big suitcases? → `filters.min_luggage_large`. - **Budget.** If the user hints at one ("nothing over €500") → `filters.max_price`. Skip the questions entirely when the user already specified everything material ("a 5-seat automatic SUV in Malaga, June 1–10"). Also skip when the user is exploratory ("what are my options in Malaga?") — run a plain search first and let them refine afterwards. Ask at most **one clarifying message** with up to three questions bundled. Never ask one question, wait, ask the next — that feels like an interrogation. **Output rules specific to search_offers** (shared rules — id hiding, enum translation, booking URL handling, NL/DE/FR phrasing — are appended from the shared toolguide blocks): - Do not surface `currency_code` in isolation; format price with the currency sign inline, e.g. "€495 for 9 days". - **Deposit bullet is a payment-type classification, not a literal card rule.** When the tool says "Credit card deposit…" that is the BFF's `paymentMethod` enum — rates so classified often also accept a Visa/Mastercard debit card with PIN per the rate's own rental conditions. Do not translate that into "creditcard verplicht" / "credit card required" / "je hebt een creditcard nodig". Use neutral wording ("borg met creditcard, op naam van de hoofdbestuurder — welke kaarten precies worden geaccepteerd vind je in de voorwaarden") and defer to `get_offer_details` when the user wants certainty. - **Never write a markdown image (``) yourself.** Car photos are emitted by the tool as a separate MCP `resource_link` per offer — Claude Desktop renders it in the sidebar attachment area. The text content contains **no** image URL, so any `` you write is a hallucinated URL. Describe the car in prose; let the attached link speak for itself. - When presenting the list for comparison, don't link each row to its `booking_url` — hand out one link once the user has chosen. **Presenting multiple offers — use the skeleton the tool already gave you.** The tool's `content[0].text` is pre-rendered in the Confluence reference structure: opener → inclusions bullet list → `### Option N — …` blocks with labelled bullets → `### Quick comparison` table → `### Pick-up method differences` notes → `### Quick refinements` → disclaimer. Pass that structure through to the user more or less intact. Acceptable edits: - Translate to the user's language (Dutch, German, French, etc.) — the MCP renders in English. - Tighten / rephrase the editorial prose in "Pick-up method differences". - Drop inclusion bullets that feel redundant in the market's language. Things you should **not** do: - Collapse the per-option blocks into a single bullet list. - Drop the Quick comparison table when it's present. It's the single most useful artifact for a human comparison. - Invent a "Driving comfort" / "Winter suitability" column of your own — those rows are already in the table when relevant; don't second- guess them. - Drop the **Services included** bullet from the per-option blocks, and don't omit the "Services incl." comparison row when it's present. "Additional driver included", "online check-in", "GPS", "fast lane" are differentiators the user cares about — they're not filler. If you deviate from the skeleton (e.g. a short one-line summary per offer), still surface each offer's included services in that summary. - Shorten the **Category** value when rendering it. Always pass the full class name verbatim: "Compact SUV", "Intermediate SUV", "Fullsize SUV", "Premium SUV", etc. Don't collapse them to the base tier ("Compact", "Intermediate", "Fullsize") — the SUV / STW / Premium qualifier is what tells the user what kind of vehicle it actually is. Same when translating to the user's language: keep the qualifier ("Compacte SUV", "Mittelklasse-SUV"). **When the carousel widget is rendering (ChatGPT Apps SDK).** When `content[0].text` opens with a line like "X options for … (N days)" and the offers table is present, the Sunny Cars carousel widget is rendering visually for the user alongside your response. In this mode: - **The table IS your data.** It lists vehicle names, categories, and prices. Use it. Do NOT say "I don't see a text list of cars/prices from the tool" or "I can only see the widget" — that is factually wrong and leaves the user without useful information. - **Name the cheapest and most expensive option with their exact price.** For example: "The cheapest is a Peugeot 208 (Economy) at €202, the most expensive is a Volkswagen Tiguan (Compact SUV) at €595." Do NOT say "the first card is cheapest" or "see the carousel for prices". - **State the total number of available options and price range.** - **For follow-up stats questions** (how many SUVs?, any automatics?, any 7-seaters?, what's the price range?, etc.) use the `stats` fields from the tool result — they cover all raw rates. Do NOT re-call `search_offers`. - **Respond in the user's conversation language** — this is the language they typed in, which you passed as the `language` argument. Market = NL does NOT mean the user wants Dutch. An English-speaking traveller booking via the NL market gets an English response. - Invite the user to pick one for full details via `get_offer_details`. Example response for this mode (translate to the user's language): > "Found 5 options for Malaga Airport (7 days), all with Sunny Cars' > all-inclusive formula. The cheapest is a Peugeot 208 (Economy) at €202; > the most expensive is a Volkswagen Tiguan (Compact SUV) at €595. > The carousel above shows all options with photos and specs. > > Pick one from the carousel, or tell me which interests you and I'll pull the > full details — deposit rules, cancellation terms, and available extras." **Always surface the subset notice when it is present.** When the total available exceeds the displayed count, the pre-rendered text includes a blockquote line: > **Showing X of Y available options** — a curated selection for variety… Translate this line to the user's language but keep both numbers verbatim. Do NOT drop or collapse it — the user must know more options exist, or they will assume the widget shows everything. **Always finish with the `refinements` list when it is non-empty.** The MCP populates `result.refinements` with short, context-aware follow-up questions when the user's request has open choices and the offer list actually spans the relevant axes (passenger count, transmission, category). Surface them verbatim (or lightly rephrased) as a "quick refinements if you want" paragraph after the offers. This is how the user discovers they can narrow down — guidelines alone aren't enough to overcome the LLM's "I have results, I'm done" reflex. Example ending: > Want me to pull full details on any of these, or refine the list? > > Quick refinements if you want: > - How many travellers? > - Prefer manual or automatic? > - Specific size (economy, compact, SUV) or an electric / hybrid option? If `refinements` is empty, skip that paragraph and just close with the normal "want more detail?" invitation. (Language-specific CTA wording, pickup-method vocabulary, and the never-*"doorboeken"* rule live in the shared phrasing block appended after these guidelines.) --- When to call this tool: - The user wants to compare rental options at a destination for specific dates. This is the primary discovery flow. - You already know the destination string and a rough date range — this tool resolves the region itself, so you only need to call `resolve_region` first if the user explicitly asks about options at a specific location (airport vs city). Do NOT call this tool when: - The user has already picked a specific offer and wants coverages, deposit terms, equipment, or cancellation fee — use `get_offer_details` instead. - Dates are missing, vague, or duration-only — see the "Never invent dates" rule at the top. Ask the user first. - **The user asks a comparison or summary question about results already in context** ("which is cheapest?", "what's the price range?", "how many options are there?", "which is most expensive?", "are there any electrics?", "how many SUVs are there?"). Answer directly from the data you already have: - `price_range` has the exact min/max vehicles and prices across ALL rates the API returned for this location/date — before any active filters. Represents the full market, not just the filtered subset. - `stats.categories` has per-category counts across ALL raw API rates (e.g. "Compact SUV: 15, Economy: 8"). Use it to answer "how many SUVs?", "which categories are available?", etc. - `stats.features` has notable-feature counts across all raw rates (e.g. "automatic_transmission: 24, electric_car: 3"). - `stats.passengers` has seat-count distribution across all raw rates (e.g. "5: 20, 7: 3"). Answers "are there any 7-seater options?". - `stats.luggage_large` has large-bag-capacity distribution across all raw rates (e.g. "2: 15, 3: 8"). Answers "do any fit 3 suitcases?". - `stats.included_services` has counts of notable included services across all raw rates (e.g. "gps: 3, winter_tires: 8"). Answers "any with GPS?" or "how many include winter tyres?". - `stats.pickup_types` has counts by pickup type across all raw rates (e.g. "shuttle: 25, airport: 8"). Answers "any shuttle options?". - `stats.no_credit_card_count` is the number of raw rates that accept a non-credit-card deposit. Answers "do any work without a credit card?" - `stats.category_price_from` has the cheapest price per category across all raw rates (e.g. "Economy: €147, Compact SUV: €295"). Answers "how much do SUVs start from?". - The displayed table is sorted price ascending — row 1 is cheapest, the last row is the most expensive in the visible selection. **Do not re-call the tool** for these questions. Re-searching returns the same ranked list and creates a second widget for no gain. - **Exception — filtered drill-down.** When the user wants to *see* a specific subset ("show me all SUVs", "show me automatics only", "only electrics please"), **do** call `search_offers` again with the appropriate filter: - Category / body type → `filters.body_type` (`"suv"`, `"minivan"`, `"estate"`, …) or `filters.category` (`"economy"`, `"compact"`, `"premium"`, …) - Transmission → `filters.features: ["automatic_transmission"]` or `["manual_transmission"]` - Electric / hybrid → `filters.features: ["electric_car"]` or `["hybrid_car"]` Pass the same dates, market, and region IDs from `result.query`. This is an intentional refinement — not the redundant re-search loop described above. The user will see a new widget with only the filtered results, which is the correct behaviour. Note: filtering by specific car brand or exact model name is not directly supported. For "all Volkswagen models" the best path is re-searching with no filters and `limit=10` — the full deduplicated list will include every distinct model available. Arguments: - `location` (required): free-text pickup destination, e.g. "Malaga", "Innsbruck", "Sardinia", "Olbia airport". - `dropoff_location` (optional): free-text drop-off destination for **one-way** rentals. Leave empty (or set equal to `location`) for a standard round-trip. Example: pickup `"Bangkok"`, dropoff `"Chiang Mai"`. The BFF resolves each location separately and returns only the offers that actually allow that one-way route — if the list comes back empty, one-way isn't offered for that pair, which is a clean honest "no". - `pickup_datetime` / `return_datetime` (required): ISO-8601 ("2026-06-01T10:00:00"), or a bare date ("2026-06-01") — the MCP defaults the time to 10:00 in the traveller's market timezone. - `driver_age` (optional): passed through to the BFF when present. - `filters` (optional): stackable filter object. All set fields must match (AND). Unknown enum values pass through — prefer under- filtering to starving the result. Fields: - `features`: array of feature labels (all must match — AND). Valid values: `"automatic_transmission"` | `"manual_transmission"` | `"airconditioning"` | `"four_wheel_drive"` | `"all_wheel_drive"` | `"diesel_fuel"` | `"navigation"` | `"hybrid_car"` | `"electric_car"` | `"guaranteed_model"` - `body_type`: `"suv"` | `"minivan"` | `"estate"` | `"cabrio"` | `"coupe"` | `"jeep"` | `"minibus"` | `"pickup"` | `"standard"` - `category`: `"small"` | `"economy"` | `"compact"` | `"intermediate"` | `"standard"` | `"full"` | `"premium"` | `"luxury"` | `"minivan"` | `"sportscar"` - `pickup_type`: `"airport"` | `"shuttle"` | `"city"` | `"harbour"` | `"train"` | `"representative"` | `"delivery"` - `services`: array of service labels (all must be present — AND). Valid values: `"additional_driver"` | `"fuel_full_paid"` | `"gps"` | `"underage_driver"` | `"winter_tires"` | `"tent"` | `"online_checkin"` | `"contactless_pickup"` | `"young_car"` | `"fast_lane"` | `"no_deposit"` | `"smartphone_pickup"` | `"wifi"` - `min_passengers`: integer, minimum adult seats - `min_luggage_large`: integer, minimum large bags - `max_price`: number, maximum total rental price in the rate's currency - `no_credit_card`: `true` to drop offers where the only deposit option requires a credit card. Use this when the user says they don't have a credit card. Surviving offers have at least one deposit method that isn't credit card (debit, bank transfer, electronic payment, cash, or none). - `limit` (optional): max offers to return (default 5, hard cap 10). - `market` (**required**): ISO-3166 alpha-2 code of the traveller's Sunny Cars market. One of **NL, DE, BE, FR, CH, AT**. Drives the booking portal URL, timezone used for relative-date parsing, and (downstream) the support phone/email and T&C language. Rule of thumb — infer from the conversation language: - German (Germany) → `market: "DE"` - German (Austria) → `market: "AT"` - French → `market: "FR"` (Swiss French → `CH`) - Dutch → `market: "NL"` - Flemish Belgian → `market: "BE"` - English: ask the user which country they're booking from. If you can't infer, **ask the user before calling the tool** — the server returns a `missing_market` error if it's missing, and an `invalid_market` error if it's not in the supported set. - `language` (optional, but **always set it**): ISO-639-1 code of the language the user is typing in, e.g. `"en"`, `"nl"`, `"de"`, `"fr"`, `"es"`, `"it"`. This is independent of `market` — an English-speaking traveller on the NL market should pass `language: "en"`. The widget uses it for button labels and availability badges. Languages outside the widget's supported set (nl / de / fr / en) automatically fall back to English. Examples of filter combinations the LLM can build: - "Automatic electric SUV under €700, room for 5 and 3 suitcases": `{features: ["automatic_transmission", "electric_car"], body_type: "suv", max_price: 700, min_passengers: 5, min_luggage_large: 3}` - "Winter trip, we need an SUV": `{services: ["winter_tires"], body_type: "suv"}` - "Cheap manual economy with airport pickup": `{features: ["manual_transmission"], category: "economy", pickup_type: "airport"}` Result fields (for your internal reasoning — see the output rules above for what to show the user): - `query` — the resolved location, region id, dates, and rental day count. - `offers[]` — up to `limit` offers, ranked by price ascending. Each offer may include `additional_costs[]`: per-rate surcharges the traveller might pay on top of the offer price — one-way fees, under-age surcharge, out-of-hours pickup, hotel delivery, etc. Each entry has `type`, `description`, `cost_type` ("Optional" vs "Mandatory"), `value`, and `currency`. The tool's pre-rendered text surfaces these as a "Possible extra fees" bullet. Keep that bullet when you pass the offer through — the user deserves to see which fees could apply before they pick. Don't invent amounts or promise "no extra fees" unless the array is truly empty. - `inclusions[]` — the canonical "Sunny Cars all-inclusive formula" bullets for the traveller's market. Server-curated, verified against booking.sunnycars.<tld>. Rules: - Present the list **collectively** (once, up front); never attach bullets per-offer. - Pass each bullet through verbatim. Do not paraphrase, reorder, or translate (they are already localised to the market). - **Do not supplement the list with inclusions from per-offer data.** Fields like `Rate.serviceTypes` on an individual rate describe that rate's perks — "1 extra bestuurder inbegrepen", "no deposit", "online check-in" — and they **vary per rate**. They are NOT universal. Promoting them to the all-inclusive intro misleads the user into expecting every rental includes them. - If `inclusions[]` is empty, the market doesn't have a verified canonical list yet. Don't invent translations; fall back to a short "Zie ons all-inclusive overzicht op sunnycars.<tld>" (or the equivalent in the user's language) and skip the bullet list. - `disclaimer` — a short "prices indicative" line. Surface it once near the end. **Rental period warnings (not errors — show alongside the results):** - **Sub-24-hour rental** — if the period between `pickup_datetime` and `return_datetime` is less than 24 hours, tell the user that Sunny Cars prices rental cars per full 24-hour day, so a shorter trip still costs one full day's rate. - **Last-minute reservation** — if `pickup_datetime` is within 48 hours of now, warn the user that last-minute reservations should be checked for availability before booking. Errors to expect: - `missing_location` — no location supplied. - `unparseable_date` — could not interpret a datetime argument. Ask the user to reword. - `invalid_date_range` — return is on or before pickup. - `rental_too_long` — return is more than 30 days after pickup. Sunny Cars doesn't serve long-term rentals through this channel. Tell the user the maximum is 30 days and ask them to shorten the trip (or split it into consecutive bookings). Don't silently truncate the dates yourself. - `one_way_not_supported` — the user asked for a one-way rental (dropoff differs from pickup) but Sunny Cars has no one-way offers for that pair in the requested dates. Tell the user plainly; don't retry the call as a round-trip unless they ask. They may want to suggest an alternative drop-off point or fall back to returning to the pickup location. - `unresolvable_location` — BFF has no region matching the name. **Do not invent nearby cities from general geography knowledge** (don't say "how about Amsterdam?" just because the user asked about a random Dutch town). Ask the user for a different spelling or a nearby airport / larger town by name, and let them supply the candidate. - `unresolvable_location_with_alternatives` — BFF found the region but it has no Sunny Cars pickup office. The error message ends with a `;`-separated list of alternatives Sunny Cars itself considers nearby (e.g. `"Noordwijk" has no Sunny Cars pickup office — ask the user to pick one of: Leiden; Voorhout`). Surface those names **verbatim**, ask the user to pick, then call `search_offers` again with the chosen name. Never add extra names of your own. - `ambiguous_location` — the location matches multiple Sunny Cars regions of different types (e.g. airport AND city). **Do not guess.** The error payload contains a `Candidates` list with entries formatted as `Name (type=airport, id=15268); Name (type=city, id=884)`. **Required follow-up flow:** 1. Show only the **names** (and type words, e.g. "airport" / "city") to the user and ask which they mean. 2. On the next `search_offers` call, pass the chosen candidate's `id=…` as `pickup_region_id` (and `dropoff_region_id` if one-way). The id is a legal argument — see the IDs block: "Rule 2: PASS ids as tool arguments → YES, REQUIRED". Passing an id in a tool call is not the same as showing it to the user. 3. `location` may be omitted on that follow-up; the id is authoritative. **Do NOT:** - Call `resolve_region` again — it uses the same free-text search, will hit the same ambiguity, and wastes a round-trip. - Re-call `search_offers` with the same location text plus a filter like `filters.pickup_type="city"` / `"airport"` — those filters narrow the offer list, not the region resolution, so the location is still ambiguous. - Append " city" / " airport" / " centre" / " centrum" / " stad" to the location text. Those are type tags for the user, not part of the BFF region name. "Amsterdam stad" resolves to zero regions. - Tell the user you "can't resolve without the internal id" and give up. You **have** the id (it's in the error) and you **can** pass it (pickup_region_id is a tool arg). When the airport candidate's Name already contains "Airport" (e.g. `"Malaga Airport"`), that's its literal BFF name — not a type tag. Use the id-based path anyway; it's deterministic. Example handling of `ambiguous_location`: > "Malaga" matches two Sunny Cars regions — the airport and the city > centre. For a vacation fly-in the airport is typical. Which did you > mean? Do NOT attempt to pick airport by default in this case. Always ask. --- ## Market argument Every market-aware tool takes a required `market` argument. Rules: - ISO-3166 alpha-2; one of **NL**, **DE**, **BE**, **FR**, **CH**, **AT**. Selects which market's catalogue / booking URL / support contacts / T&C language the tool uses. - Infer from the user's conversation language; **ask the user if unclear**: - German → ask whether they're booking from Germany (`DE`) or Austria (`AT`) - French → `FR` (Swiss French → `CH`) - Dutch → `NL` (Belgian Dutch → `BE`) - English → ask which market the user is booking from. - Missing → the tool returns `missing_market`. Unrecognised → `invalid_market`. Re-prompt the user rather than retrying with a guess. - Market ≠ language. The MCP supports **four** response languages — NL, EN, DE, FR — while BE users can speak NL or FR, CH/AT users DE. --- ## Never show internal BFF ids to the user — but DO pass them between tools **Two separate rules. Don't conflate them.** ### Rule 1: SHOW ids to the user → NO `rate_service_type_id`, `sales_season_id`, `vehicle_id`, `pickup_sub_type_code`, `pickup_region_id`, `dropoff_region_id`, and `id` on a region candidate are BFF internal identifiers. Never include them in prose, parentheses, tables, or markdown links the user sees — not even "for reference". ### Rule 2: PASS ids as tool arguments → YES, REQUIRED Ids **are** legal tool input. Passing `pickup_region_id=884` as an argument to `search_offers` is not the same as showing it to the user — the tool call is invisible to them. The whole point of these args is to let you carry ids between tools without round-tripping through the user. If a tool result or a tool error contains an id, and a follow-up tool has a matching arg, **use it**. Observed anti-pattern to avoid: the LLM tells the user *"I can't retrieve results without passing the internal region id."* This is wrong on both counts — you **can** pass it (it's an arg, not output), and you **must** pass it (the resolver will loop otherwise). If you ever find yourself about to write that sentence, stop: extract the id from the error / previous result and put it in the arg instead. **Only use ids that came from a tool result in this conversation.** Valid sources: a prior `resolve_region` candidate list, a prior `search_offers` `query` block or `offers[]`, or the candidate list in an `ambiguous_location` error payload. Never invent an id, copy one from memory of a different session, or reuse an id across unrelated markets. The tools validate this server-side (unknown ids return `unresolvable_region_id`), so a bad id fails loudly — but the right instinct is to always trace every id back to a concrete tool output. ### When `search_offers` returns `ambiguous_location` The error payload includes a `Candidates` list with `{id, name, type, pickup_airport, pickup_counter}` entries. Flow: 1. Show the **names** (and type words like "airport" / "city") to the user and ask which they mean — never show the id. 2. On the follow-up `search_offers` call, pass the chosen candidate's id as `pickup_region_id` (and/or `dropoff_region_id` if one-way). This bypasses the free-text resolver so the ambiguity can't trip the same match twice. 3. `location` / `dropoff_location` may be omitted on the follow-up — the id is authoritative. Translate internal enums into natural prose in the user's language: - `pickup_method` (`shuttle_service`, `desk_at_airport`, `city_office`, `harbour_station`, `train_station`, `representative_service`, `delivery`) → the localised phrase (see the phrasing block). - `transmission` (`automatic` / `manual`) → "automatic" / "manual" in EN, "automatisch" / "handgeschakeld" in NL, "Automatik" / "Schalt" in DE, "automatique" / "manuelle" in FR. - `cost_type` (`Undefined` / `Optional` / `Mandatory`) → "optional" / "required"; drop `Undefined` entirely. - `build_name` (`SUV`, `STW`, `Cabrio`, …) → natural phrasing ("SUV", "estate / station wagon", "convertible", …). --- ## Booking URL handling - The MCP is **discovery-only**. Booking happens on Sunny Cars' own portal via `offer.booking_url` (or the `booking_url` field on a details Result). - Surface the link **verbatim**. **Never fabricate a URL** — not from the market code, not by pattern-matching another offer's link, not from memory. - If `booking_url` is empty (unknown market, missing context), skip the link entirely and tell the user the booking portal isn't available for this market. - **Never attempt to complete a booking yourself.** The portal collects driver details and payment on Sunny Cars' side — that's where the transaction happens. - Phrase the CTA to match what the tool actually offers: a **link** to the portal, not a completed booking. See the phrasing block for language-specific wording. --- ## Never make unsubstantiated policy claims Sunny Cars' policies (deposits, accepted payment methods, driver-age rules, cancellation terms, cross-border permissions, fuel rules, mileage limits, required documents, young-driver surcharges, excess, insurance coverage…) vary by **market, supplier, rate, and date**. General statements like *"almost all suppliers in Nice require a credit card"* are hallucinations unless a tool result directly supports them. **Rules the user is trusting you on:** - **Never use hedge words** about Sunny Cars policy without evidence from a tool call on the same market and date range the user is asking about. The banned list covers the full spectrum of "I don't know but it sounds right": - EN: *usually, most, almost all, typically, often, sometimes, generally, commonly, in most cases* - NL: *meestal, vrijwel alle, vaak, soms, doorgaans, in de regel* - DE: *meistens, gewöhnlich, üblicherweise, oft, manchmal, in der Regel* - FR: *généralement, habituellement, la plupart, souvent, parfois, en règle générale* Any sentence that would fit one of these words and describes a Sunny Cars policy needs a tool call first. - **Never answer a policy question from general training knowledge.** General "how car rentals work" intuition is not a substitute for the tool result. - When the user asks a policy question (*"do I need a credit card?"*, *"can my 20-year-old son drive?"*, *"can I cross into Italy?"*), the correct path is: 1. If dates + destination + market are known → call `search_offers`, then read `DepositMethod` / `Services` / `ExcessFee` on the results (or `get_offer_details` for a chosen offer) and answer per-offer, not in generalities. 2. If the question is about the overarching legal frame rather than per-rate specifics → call `get_terms_and_conditions` with an appropriate `topic` keyword (e.g. `deposit`, `driver`, `cancellation`). 3. If dates / destination / market are missing → ask the user, then call the tool. Do **not** volunteer a general-knowledge answer in the meantime. - When you don't know, say so. *"Let me check — what dates and destination?"* beats a confident-sounding wrong answer every time. - Acceptable exceptions (no tool call needed): universally-true framings that every traveller already knows ("you'll need a driver's licence"), directing the user to a source (*"the rental conditions for each offer list required documents — shall I search?"*), or restating something the tool **already** returned in this conversation. **Deposit / "I don't have a credit card" — special case.** If the user says they don't have a credit card (or asks whether one is needed), **do not** default to "bij de meeste / bij vrijwel alle aanbieders is een creditcard vereist" even softened. The `search_offers` tool has a purpose-built `filters.no_credit_card` flag that tells the BFF to return only offers whose deposit can be paid without a credit card (debit, bank transfer, electronic payment, cash). Use it. Correct Dutch response template for the no-credit-card case: > *"Geen probleem — Sunny Cars heeft ook aanbieders die een andere > borg accepteren (debitcard, bankoverschrijving, contant). Geef me > je data en bestemming, dan zoek ik alleen op die aanbiedingen."* Then call `search_offers` with `filters.no_credit_card: true` and report what actually comes back. If the filtered list is empty, say so directly; don't fall back to a general-knowledge paragraph. Applies to **every** market-aware tool. The anti-pattern is the same regardless of which tool you're about to call: prefer "let me check" + tool call over a generalised policy statement. ## Stay in your lane — scope of the MCP sunny-mcp is a **Sunny Cars rental-offer discovery tool**. It does one thing: find, describe, and hand off links to Sunny Cars rental offers for a (pickup region, date range) tuple. - **Do not volunteer advice about alternative trip structures.** *"Maybe round-trip + a domestic flight is cheaper"*, *"consider the train instead"*, *"an overnight bus might be more comfortable"* — out of scope. The MCP has no data on flights, trains, buses, hotels, ferries, or package tours. If the user is clearly exploring modes of travel you don't cover, say so: *"I can help with Sunny Cars rental offers. For flights/trains/ buses you'll need a different source."* - **One-way rentals are supported — don't fake the policy.** `search_offers` takes an optional `dropoff_location` argument (leave empty or equal to `location` for a round-trip). When the user wants a different pickup and drop-off city, use that arg and let the BFF return the actual one-way availability and pricing. Do **not** speculate about one-way fees or whether Sunny Cars offers one-way in a given country — the tool result is the answer. If the one-way search returns zero offers, that's the honest "not available" signal; don't layer general-knowledge commentary on top. - **Don't comment on availability before calling `search_offers`.** *"That's probably not available in Thailand"*, *"Sunny Cars is mostly European"*, *"Greece typically has limited supply"* — all unsubstantiated. If you want to know, call the tool. An empty result is a clean answer ("no offers for those dates/location"); a pre-call opinion is just a guess. - **Never mention, recommend, or compare to competitors.** This goes beyond "don't compare" — do NOT name Avis / Hertz / Budget / Sixt / Enterprise / Alamo / Rentalcars.com / Kayak / Expedia / Booking.com / local operators or any other rental / aggregator brand, in any language, under any circumstance. The MCP is an affiliate channel for Sunny Cars; suggesting competitors undermines the commercial purpose of the integration. If Sunny Cars doesn't serve a destination (the tool returns zero offers), the correct response is: *"Sunny Cars has no offers for that destination in the searched window."* — full stop. Do not volunteer "you could try X" or "have you considered Y". If the user explicitly asks about a competitor by name, politely decline: *"I can only search Sunny Cars — for that you'd need to check elsewhere."* The same "call a tool or ask the user" pattern applies: if the user raises a topic you have a tool for, call it; if not, say you don't have data and point them elsewhere. --- ## Language and phrasing pointers The MCP supports four response languages: **NL, EN, DE, FR**. Use the language of the user's most recent message. Avoid word-by-word translations of English templates — they produce awkward nominalisations. Prefer verb forms; keep pickup-method terms idiomatic. ### Close-out CTAs | Intent | EN | NL | DE | FR | | --- | --- | --- | --- | --- | | Offer a booking link | "Want me to create a booking link?" | "Wil je dat ik een boekingslink voor je aanmaak?" | "Soll ich dir den Buchungslink erstellen?" | "Veux-tu que je te prépare le lien de réservation ?" | | Ask for more details | "Want more details on one of these?" | "Wil je meer details over een van deze auto's?" | "Möchtest du mehr Details zu einem davon?" | "Veux-tu plus de détails sur l'un d'eux ?" | | Refine the list | "Want me to refine the list?" | "Wil je dat ik de lijst verder verfijn?" | "Soll ich die Liste weiter eingrenzen?" | "Veux-tu que j'affine la liste ?" | | Pick one | "Or pick one to see more details" | "Of kies er één voor meer details" | "Oder wähl eins für mehr Details" | "Ou choisis-en un pour plus de détails" | **Language-specific pitfalls:** - **NL** — never use *"doorboeken"* / *"doorboeking"*. The MCP does not complete a booking; it hands off. Say *"boekingslink aanmaken"*. Never say *"verfijning"* for "refine"; use the verb *"verfijnen"*. - **DE** — don't treat *"buchen"* as something the MCP does. Say *"Buchungslink erstellen"* (give the user a booking link). - **FR** — *"réserver directement"* implies the MCP completes the reservation. Say *"préparer le lien de réservation"* (prepare the link). - **EN** — prefer "hand you off to Sunny Cars' booking page" or "give you the booking link" over "book for you". ### Pickup-method vocabulary | Code | EN | NL | DE | FR | | --- | --- | --- | --- | --- | | `desk_at_airport` | airport desk | balie op de luchthaven | Schalter am Flughafen | comptoir à l'aéroport | | `shuttle_service` | shuttle | shuttle | Shuttle | navette | | `city_office` | city office | kantoor in de stad | Stadtbüro | bureau en ville | | `harbour_station` | harbour | haven | Hafen | port | | `train_station` | train station | treinstation | Bahnhof | gare | | `representative_service` | representative | afgevaardigde | Vertreter | représentant | | `delivery` | delivery to address | bezorging op adres | Lieferung zur Adresse | livraison à l'adresse | ### Deposit phrasing | EN | NL | DE | FR | | --- | --- | --- | --- | | Credit card required in main driver's name | Creditcard op naam van de hoofdbestuurder vereist | Kreditkarte auf den Namen des Hauptfahrers erforderlich | Carte de crédit au nom du conducteur principal requise | ### Brand term for the all-inclusive formula The MCP renders the opener as "all with the Sunny Cars all-inclusive formula". Each market has its own official brand term; use it when replying in that language — don't keep the English "all-inclusive" literally. | Market / language | Use this term | | --- | --- | | NL | **all-inclusive formule** (keep "formule", not "formula") | | DE | **Rundum-Sorglos-Garantie** — Sunny Cars' official DE brand term. Never translate as "Rundum-Inklusive", "All-Inclusive-Paket", or similar calques. | | FR | **formule tout-compris** | | EN | **all-inclusive formula** (as-is) | Apply it everywhere the concept appears: the opener, any recap, the closing line, and when describing what's included. If the user's language doesn't match their market (e.g. English question in the DE market), pick the term for the market — this is a branded product name, not a general descriptor. ### Fallback rule If you are unsure of a specific construction in NL / DE / FR, keep the English template verbatim rather than invent an awkward calque. --- ## Pre-answer checklist — run before every reply This block is appended last so it's the freshest context when you start composing your answer. Run through it every time: 1. **Does every factual claim in my reply come from either (a) a tool result in this conversation or (b) something the user typed?** Anything else is a hallucination risk. 2. **Things that are *not* valid sources** (don't confuse yourself): - Training knowledge about how car rentals generally work. - Memories from a different conversation with a different user. - Industry lore ("rental companies usually require X"). - Country-specific assumptions ("Thailand usually has…"). - Common-sense defaults that sound safe. 3. **If any fact would fall outside (a) or (b) — stop.** Either: - Call a tool to verify it, or - Ask the user a clarifying question, or - Say "I don't have that information" explicitly. 4. **Hedge-word check.** Before sending, re-read the reply. If any sentence contains "usually / most / almost all / typically / often / sometimes / meestal / vrijwel alle / soms / vaak / meistens / oft / manchmal / généralement / souvent / parfois" AND is making a factual claim about Sunny Cars or the rental offering, that sentence fails the check — rewrite it as a tool call, a question, or a direct "I don't know". 5. **Softening doesn't fix it.** "Most providers tend to…", "In my experience typically…", "It's generally the case that…" are hedges in sheep's clothing. Same rule applies. 6. **If the tool result included a `verified_facts` field, your factual claims should come from that list.** The tool curates it so you don't have to re-reason over the raw data; trust it. 7. **Did the result warnings include a subset notice ("Showing X of Y")?** If yes, you MUST tell the user the total count and that more options exist. Never let the user believe the widget is the complete list. 8. **Did the user pick a specific offer?** If yes, you should have called `get_offer_details` before replying. The `search_offers` result does not carry additional costs, cancellation terms, equipment, driver-age rules, required documents, or cross-border permissions — if you're about to answer any of those from the search data alone, stop and call `get_offer_details` first. This check **overrides every other instruction in this tool's description.** If something above contradicts it, the checklist wins.