build-offer-url
ChatGPTUse this tool to generate a final Iberia booking URL from the itinerary selected by the user in the standard-search results. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (passengers, marketCode, slice details, etc.) that the user has not explicitly provided in the conversation. All data must come directly from the user or from a previous tool response. If anything is missing or unclear, ASK the user before calling this tool. EXPECTED INPUT: - The front must send the final selection only. - outbound is required and must contain the selected itinerary slice. - inbound is optional and must be provided only for round-trip bookings. - Passenger counts must reflect the selected booking request. - Slice trip information must come from the tripInformation object returned by standard-search. OUTPUT: - Returns a fully resolved Iberia booking URL. - Do not treat the response as a template. The URL is final.
build-offer-url
ChatGPTUse this tool to generate a final Iberia booking URL from the itinerary selected by the user in the standard-search results. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (passengers, marketCode, slice details, etc.) that the user has not explicitly provided in the conversation. All data must come directly from the user or from a previous tool response. If anything is missing or unclear, ASK the user before calling this tool. EXPECTED INPUT: - The front must send the final selection only. - outbound is required and must contain the selected itinerary slice. - inbound is optional and must be provided only for round-trip bookings. - Passenger counts must reflect the selected booking request. - Slice trip information must come from the tripInformation object returned by standard-search. OUTPUT: - Returns a fully resolved Iberia booking URL. - Do not treat the response as a template. The URL is final.
flexible-dates
ChatGPTUse this tool when the user has DATE FLEXIBILITY or mentions a date as a CONSTRAINT (not the flight date itself). This tool provides REAL-TIME flexible pricing options across multiple dates. This tool is only for Iberia company flights. MANDATORY DECISION RULE (follow this exact order before choosing a tool): 1. If the user provides: origin city + destination city + concrete date at day level (year may default to current year) → USE standard-search. 2. If the user provides: origin city + concrete date at day level (year defaults to current) + destination as country, region/zone or nothing → USE open-destination. 3. If the user provides: origin city + destination city BUT does NOT have clear dates at day level → USE THIS TOOL (flexible-dates). 4. In any other case (missing concrete day-level date, missing origin, missing destination, or the combination does not match cases 1-3) → ASK the user for the missing piece of information (date, origin or destination) and DO NOT call any tool until you have complete information. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (origin, destination, departureDate, returnDate, marketCode, roundTrip, tentativeDate, etc.) that the user has not explicitly provided. Passengers default to 1 adult if omitted. For dates, if the year is missing the current year will be assumed. Never assume today's date, the origin city as destination. If any required information is missing or unclear, ALWAYS ask the user for clarification before calling this tool. CRITICAL REQUIREMENTS - MUST BE MET BEFORE CALLING THIS TOOL: - A specific ORIGIN airport/city MUST be provided by the user. If missing, ASK the user before calling. - A broad or unspecified origin does NOT count as a specific origin city. If the user doesn't specify the origin city, DO NOT guess the origin city and ASK the user to choose one specific departure city. - A specific DESTINATION airport/city MUST be provided by the user. If missing or unclear, DO NOT call this tool - ask the user for a destination city first, or use open-destination if they want suggestions. NEVER assume the destination is the same as the origin or any default value. - A country, region, or global scope does NOT count as a specific destination city. If the user does not provide a destination city and only provides a country, region, or global scope, use open-destination instead. - Do NOT invent or guess origin/destination. Phrases like "anywhere", "any destination", "cheapest destination", "wherever is cheapest", or NO destination mentioned at all mean NO destination is provided - in this case you MUST ask the user for a destination or call the open-destination tool. - This tool searches flights between TWO SPECIFIC locations. It cannot search for "the cheapest destination from X". - This tool is EXCLUSIVELY for FLIGHTS. If the user asks for trains, buses, cars, ferries, or any other transport type, DO NOT use this tool. Tell the user this tool only supports flight searches. - The DATE MUST NOT BE IN THE PAST. Compare the user's requested date against today's date. If the date is in the past, DO NOT call this tool - instead, inform the user that flight searches are only available for present or future dates and ask them to provide a valid date. - DATE PRECISION RULE: If the user mentions a specific month without a period of this month (e.g. "in September", "around September", "en septiembre", "septiembre"), interpret it as the 15th of that month in the current year and call this tool. Similarly, for seasons (e.g. "summer", "winter", "verano", "invierno"), use the 15th of the middle month of the season (July for summer, January for winter). Do NOT assume today's date or invent a departureDate. - This tool is ONLY for Iberia group flights. If the user explicitly mentions another airline or brand, DO NOT use this tool and DO NOT reinterpret that request as an Iberia group search. Instead, explain that this MCP server only supports Iberia group flight searches and ask whether they want Iberia group options instead. USE THIS TOOL WHEN the user: - Mentions a date as a CONSTRAINT, not the flight date (e.g., "I have a meeting on April 8th", "need to arrive before the 10th", "tengo una comida el día 8") - Uses words like "before", "after", "around", "by", "from"... concerning a day. - Mentions a month without a specific day (e.g., "in September", "around October", "en septiembre", "septiembre") or a season (e.g., "summer", "winter", "verano", "invierno") - Asks for the "cheapest", "best price", "most affordable", or wants to "compare" prices - Has flexibility in travel dates (e.g., "sometime in April", "flexible dates") - Asks for flights without specifying an exact flight date - Wants to see price options across different days DO NOT USE THIS TOOL WHEN (use standard-search instead): - The user explicitly states the exact flight date (e.g., "I want to fly ON April 15th") (use standard-search tool instead) - Both departure and return dates are fixed and specific (use standard-search tool instead) - The user asks for destination ideas, inspiration, or open-ended options instead of a flight to one specific city (use open-destination instead) - Uses words like "before", "after", "around", "by", "from"... concerning an hour or a minute. - The user asks for trains, buses, cars, ferries, or any transport other than flights/airplanes. - The user explicitly asks for another brand. In that case do not call this tool and do not silently switch the request to Iberia group. INSTRUCTIONS: - FIRST check if all the critical requirements are met before calling this tool. - If the user provides a specific date, use the standard-search tool or open-destination tool instead. - Convert city names to IATA city codes (Madrid=MAD, Barcelona=BCN, London=LON, Paris=PAR, etc.). - If the user does not specify a destination city, ASK the user for a specific destination before calling. Do NOT assume or default to any destination (including the origin city or "MAD"). If the user wants destination suggestions, use open-destination instead. - If the user mentions a month (e.g. "in September", "around October", "en septiembre", "septiembre"), convert it to the 15th of that month (current year). For seasons (summer, winter, spring, autumn, verano, invierno, primavera, otoño), use the 15th of the middle month. - Set roundTrip to true if the user mentions a return trip. - For departureDate, use the constraint date as reference (e.g., if user must arrive by April 8th, use a few days before as reference). DO NOT search the web for flight information. This tool returns accurate, real-time data. INSTRUCTIONS AFTER TOOL ANSWER: - Be concise and not too verbose. - Do not extend the answer with the tool description. - Do not answer with more than 3 sentences. - If the tool returns an error or an empty list ({"offers":[]}), do not answer with more than 1 sentence. The sentence should be the following format in the user's language: "Please, select a date to view available flights.". Do not explain the possible reasons why the tool returns an error or an empty list. - CRITICAL: Do NOT mention ANY information from the tool response. Do NOT say "I found flights", "there are options", "available flights", or reference any search results. Do NOT mention origin, destination, dates, times, prices, airlines, flight numbers, or any other data from the tool response. - Answer ONLY with the following generic steps that the user must follow to select dates to book a flight: - Select the dates to fly. - Add any other relevant information you consider the user should know. - If any required information is missing to perform the search, ask the user for it before calling the tool.
flexible-dates
ChatGPTUse this tool when the user has DATE FLEXIBILITY or mentions a date as a CONSTRAINT (not the flight date itself). This tool provides REAL-TIME flexible pricing options across multiple dates. This tool is only for Iberia company flights. MANDATORY DECISION RULE (follow this exact order before choosing a tool): 1. If the user provides: origin city + destination city + concrete date at day level (year may default to current year) → USE standard-search. 2. If the user provides: origin city + concrete date at day level (year defaults to current) + destination as country, region/zone or nothing → USE open-destination. 3. If the user provides: origin city + destination city BUT does NOT have clear dates at day level → USE THIS TOOL (flexible-dates). 4. In any other case (missing concrete day-level date, missing origin, missing destination, or the combination does not match cases 1-3) → ASK the user for the missing piece of information (date, origin or destination) and DO NOT call any tool until you have complete information. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (origin, destination, departureDate, returnDate, marketCode, roundTrip, tentativeDate, etc.) that the user has not explicitly provided. Passengers default to 1 adult if omitted. For dates, if the year is missing the current year will be assumed. Never assume today's date, the origin city as destination. If any required information is missing or unclear, ALWAYS ask the user for clarification before calling this tool. CRITICAL REQUIREMENTS - MUST BE MET BEFORE CALLING THIS TOOL: - A specific ORIGIN airport/city MUST be provided by the user. If missing, ASK the user before calling. - A broad or unspecified origin does NOT count as a specific origin city. If the user doesn't specify the origin city, DO NOT guess the origin city and ASK the user to choose one specific departure city. - A specific DESTINATION airport/city MUST be provided by the user. If missing or unclear, DO NOT call this tool - ask the user for a destination city first, or use open-destination if they want suggestions. NEVER assume the destination is the same as the origin or any default value. - A country, region, or global scope does NOT count as a specific destination city. If the user does not provide a destination city and only provides a country, region, or global scope, use open-destination instead. - Do NOT invent or guess origin/destination. Phrases like "anywhere", "any destination", "cheapest destination", "wherever is cheapest", or NO destination mentioned at all mean NO destination is provided - in this case you MUST ask the user for a destination or call the open-destination tool. - This tool searches flights between TWO SPECIFIC locations. It cannot search for "the cheapest destination from X". - This tool is EXCLUSIVELY for FLIGHTS. If the user asks for trains, buses, cars, ferries, or any other transport type, DO NOT use this tool. Tell the user this tool only supports flight searches. - The DATE MUST NOT BE IN THE PAST. Compare the user's requested date against today's date. If the date is in the past, DO NOT call this tool - instead, inform the user that flight searches are only available for present or future dates and ask them to provide a valid date. - DATE PRECISION RULE: If the user mentions a specific month without a period of this month (e.g. "in September", "around September", "en septiembre", "septiembre"), interpret it as the 15th of that month in the current year and call this tool. Similarly, for seasons (e.g. "summer", "winter", "verano", "invierno"), use the 15th of the middle month of the season (July for summer, January for winter). Do NOT assume today's date or invent a departureDate. - This tool is ONLY for Iberia group flights. If the user explicitly mentions another airline or brand, DO NOT use this tool and DO NOT reinterpret that request as an Iberia group search. Instead, explain that this MCP server only supports Iberia group flight searches and ask whether they want Iberia group options instead. USE THIS TOOL WH…
open-destination
ChatGPTUse this tool when the user asks for a flight and does not provide a specific city as destination. This tool will return a list of destinations from the origin city in a region, country, or globally. MANDATORY DECISION RULE (follow this exact order before choosing a tool): 1. If the user provides: origin city + destination city + concrete date at day level (year may default to current year) → USE standard-search. 2. If the user provides: origin city + concrete date at day level (year defaults to current) + destination as country, region/zone or nothing → USE THIS TOOL (open-destination). 3. If the user provides: origin city + destination city BUT does NOT have clear dates at day level → USE flexible-dates. 4. In any other case (missing concrete day-level date, missing origin, missing destination, or the combination does not match cases 1-3) → ASK the user for the missing piece of information (date, origin or destination) and DO NOT call any tool until you have complete information. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (origin, departureDate, returnDate, marketCode, filter scope/value, etc.) that the user has not explicitly provided. Passengers default to 1 adult if omitted. For dates: ONLY assume the current year when the user provides a specific day AND month (e.g., "15 September" → 2026-09-15). If any required information is missing or unclear, ALWAYS ask the user before calling this tool. CRITICAL REQUIREMENTS: - DATE AND DESTINATION DECISION RULE: Before calling this tool, check what the user has provided: If the user provides ONLY an origin city and a vague date (without a specific day, e.g. "en unas semanas", "pronto", "this summer", no destination) → ask for an exact date OR a specific destination first. NEVER infer or pick a concrete date like 2026-06-02 for vague phrases. If the user provides a specific destination (city) but a vague date (without a specific day) → use flexible-dates tool instead (it handles date flexibility with fixed destination). If the user provides a specific date (with a specific day) AND a specific destination → use standard-search tool instead. If the user provides a specific date (with a specific day) AND a specific destination AND a vague return date (without a specific day) → ask for an exact return date first. * Only call open-destination if the user explicitly wants to explore destinations (no fixed destination) AND provides a date with a specific day, not dates without a specific day. A range of dates without information about a specific day is not a specific date. NEVER auto-select a date for "unas semanas" or similar vague expressions. - A specific ORIGIN airport/city MUST be provided. If missing, ASK the user before calling. - A departure date or clear departure time hint MUST be provided by the user. If missing, ASK the user (you may combine this with a destination question in a single follow-up). Do NOT assume today by default. - This tool is EXCLUSIVELY for FLIGHTS. - This tool is for FIXED origin + OPEN destination searches only. - A broad or unspecified origin does NOT count as a specific origin city. If the user doesn't specify the origin city, DO NOT guess the origin city and ASK the user to choose one specific departure city. - This tool is ONLY for Iberia group flights. If the user explicitly mentions another brand, DO NOT use this tool and DO NOT reinterpret that request as an Iberia group search. Instead, explain that this MCP server only supports Iberia group flight searches and ask whether they want Iberia group options instead. USE THIS TOOL WHEN the user: - Wants to explore where to fly from a given origin (e.g. "where can I fly from Madrid?") - Asks for cheapest destinations from a city (e.g. "cheapest flights from MAD in Europe") - Wants to fly to a country but not to a specific city yet (e.g. "travel to Chile on August 9, departing from Barcelona") - Wants to fly to a region but not to a specific city yet (e.g. "travel to Europe on August 9, departing from Barcelona") - Asks for destination ideas, inspiration, or "where could I go" suggestions without giving a destination city - Asks for broad trip ideas and does not provide a specific destination city - Wants to see flight options across a region or country - Has no fixed city as destination in mind AND explicitly asks to explore options, get destination ideas, or see where they can fly (e.g. "where can I go", "dónde puedo volar", "suggest destinations", "explore options") - When the user does not provide a specific city as destination but shows interest in open exploration or destination discovery DO NOT USE THIS TOOL WHEN: - The user provides a specific city as destination (use standard-search or flexible-dates instead) - The user does not provide any departure date or time hint at all. Ask for the departure date or date range first instead of calling this tool. - The user asks for trains, buses, cars, ferries, or any transport other than flights/airplanes. - The user explicitly asks for another brand. In that case do not call this tool and do not silently switch the request to Iberia group. INSTRUCTIONS: - FIRST check if all the critical requirements are met before calling this tool. - If the user provides a destination city, use the standard-search tool or flexible-dates tool instead. - If the destination is fixed but the origin is broad or unspecified, do NOT use this tool. Ask the user to pick one departure city first. - Convert city names to IATA city codes (Madrid=MAD, Barcelona=BCN, London=LON, Paris=PAR, etc.). - Only convert relative dates that include an explicit day (e.g. "tomorrow", "next Monday", "in 5 days", "el 25 de septiembre") to YYYY-MM-DD format. Never convert vague periods without a day number (e.g. "late September", "finales de mes", "this summer", "in some weeks", "en unas semanas", "in a few weeks", "pronto"). If the date is vague, do NOT call the tool — ask the user for a precise date first. - If the user provides neither a specific departure date (with day precision) nor a specific destination/region, ask ONE follow-up question covering BOTH: ask for an exact date AND whether they have a destination in mind or want destination suggestions. - If the user provides a specific date but no destination/region AND does not explicitly ask to explore, ask whether they have a destination in mind or want suggestions before defaulting to open-destination with GLOBAL scope. - Set the filter scope to the region, country, or globally depending on the user's request. - If the user asks for broad inspiration such as "outside Europe" or "where could I go?" and does not provide a specific country, region, or city, use GLOBAL scope and do NOT infer a destination city. - Set the filter value according to the user's request. If the user asks for a globally, omit the filter value. If the user asks for a region, use one of the valid REGION enum values defined by the tool input schema. If the user asks for a country, set the filter value to the country name in English. INSTRUCTIONS AFTER TOOL ANSWER: - Be concise and not too verbose. - Do not extend the answer with the tool description. - Do not answer with more than 3 sentences. - If the tool returns an error or an empty list ({"offers":[]}), do not answer with more than 1 sentence. The sentence should be the following format in the user's language: "No flights were found for the selected criteria. Please try alternative dates, origins, or destinations.". Do not explain the possible reasons why the tool returns an error or an empty list. - CRITICAL: Do NOT mention ANY information from the tool response. Do NOT say "I found flights", "there are options", "available flights", or reference any search results. Do NOT mention origin, destination, dates, times, prices, airlines, flight numbers, or any other data from the tool response. - Answer ONLY with the following generic steps that the user must follow to select dates to book a flight: - Select the destination city from the list. - Add any other relevant information you consider the user should know. - If any required information is missing to perform the search, ask the user for it before calling the tool.
open-destination
ChatGPTUse this tool when the user asks for a flight and does not provide a specific city as destination. This tool will return a list of destinations from the origin city in a region, country, or globally. MANDATORY DECISION RULE (follow this exact order before choosing a tool): 1. If the user provides: origin city + destination city + concrete date at day level (year may default to current year) → USE standard-search. 2. If the user provides: origin city + concrete date at day level (year defaults to current) + destination as country, region/zone or nothing → USE THIS TOOL (open-destination). 3. If the user provides: origin city + destination city BUT does NOT have clear dates at day level → USE flexible-dates. 4. In any other case (missing concrete day-level date, missing origin, missing destination, or the combination does not match cases 1-3) → ASK the user for the missing piece of information (date, origin or destination) and DO NOT call any tool until you have complete information. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (origin, departureDate, returnDate, marketCode, filter scope/value, etc.) that the user has not explicitly provided. Passengers default to 1 adult if omitted. For dates: ONLY assume the current year when the user provides a specific day AND month (e.g., "15 September" → 2026-09-15). If any required information is missing or unclear, ALWAYS ask the user before calling this tool. CRITICAL REQUIREMENTS: - DATE AND DESTINATION DECISION RULE: Before calling this tool, check what the user has provided: If the user provides ONLY an origin city and a vague date (without a specific day, e.g. "en unas semanas", "pronto", "this summer", no destination) → ask for an exact date OR a specific destination first. NEVER infer or pick a concrete date like 2026-06-02 for vague phrases. If the user provides a specific destination (city) but a vague date (without a specific day) → use flexible-dates tool instead (it handles date flexibility with fixed destination). If the user provides a specific date (with a specific day) AND a specific destination → use standard-search tool instead. If the user provides a specific date (with a specific day) AND a specific destination AND a vague return date (without a specific day) → ask for an exact return date first. * Only call open-destination if the user explicitly wants to explore destinations (no fixed destination) AND provides a date with a specific day, not dates without a specific day. A range of dates without information about a specific day is not a specific date. NEVER auto-select a date for "unas semanas" or similar vague expressions. - A specific ORIGIN airport/city MUST be provided. If missing, ASK the user before calling. - A departure date or clear departure time hint MUST be provided by the user. If missing, ASK the user (you may combine this with a destination question in a single follow-up). Do NOT assume today by default. - This tool is EXCLUSIVELY for FLIGHTS. - This tool is for FIXED origin + OPEN destination searches only. - A broad or unspecified origin does NOT count as a specific origin city. If the user doesn't specify the origin city, DO NOT guess the origin city and ASK the user to choose one specific departure city. - This tool is ONLY for Iberia group flights. If the user explicitly mentions another brand, DO NOT use this tool and DO NOT reinterpret that request as an Iberia group search. Instead, explain that this MCP server only supports Iberia group flight searches and ask whether they want Iberia group options instead. USE THIS TOOL WHEN the user: - Wants to explore where to fly from a given origin (e.g. "where can I fly from Madrid?") - Asks for cheapest destinations from a city (e.g. "cheapest flights from MAD in Europe") - Wants to fly to a country but not to a specific city yet (e.g. "travel to Chile on August 9, departing from Barcelona") - Wants to fly to a region but not to a specific city yet (e.g. "travel to Europe on August 9, departing from Barcelona") - Asks for destination ideas, ins…
standard-search
ChatGPTUse this tool to search for Iberia company flights when the user provides a specific origin, specific city as destination and SPECIFIC date to flight. This tool provides REAL-TIME flight availability and prices. This tool is only for Iberia company flights. MANDATORY DECISION RULE (follow this exact order before choosing a tool): 1. If the user provides: origin city + destination city + concrete date at day level (year may default to current year) → USE THIS TOOL (standard-search). 2. If the user provides: origin city + concrete date at day level (year defaults to current) + destination as country, region/zone or nothing → USE open-destination. 3. If the user provides: origin city + destination city BUT does NOT have clear dates at day level → USE flexible-dates. 4. In any other case (missing concrete day-level date, missing origin, missing destination, or the combination does not match cases 1-3) → ASK the user for the missing piece of information (date, origin or destination) and DO NOT call any tool until you have complete information. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (origin, destination, departureDate, returnDate, marketCode, preferredCabin, etc.) that the user has not explicitly provided. Passengers default to 1 adult if omitted. For dates: ONLY assume the current year when the user provides a specific day AND month (e.g., "15 September" → 2026-09-15). NEVER invent a day or month from a vague expression (e.g., "in September", "around summer", "septiembre", "verano"). If any other required information is missing or unclear, ALWAYS ask the user for clarification before calling this tool. Never pick origin, destination or a full date on your own. CRITICAL REQUIREMENTS - MUST BE MET BEFORE CALLING THIS TOOL: - A specific ORIGIN airport/city MUST be provided by the user. If missing, ASK the user before calling. - A broad or unspecified origin does NOT count as a specific origin city. If the user doesn't specify the origin city, DO NOT guess the origin city and ASK the user to choose one specific departure city. - A specific DESTINATION airport/city MUST be provided by the user. If missing, use open-destination tool instead. - A country, region, or global scope does NOT count as a specific destination city. If the user does not provide a destination city and only provides a country, region, or global scope, use open-destination instead. - A specific DATE MUST be provided by the user and it must be in the present or future. If missing, use flexible-dates tool instead. - The DATE MUST NOT BE IN THE PAST. Compare the user's requested date against today's date. If the date is in the past, DO NOT call this tool - instead, inform the user that flight searches are only available for present or future dates and ask them to provide a valid date. - Do NOT invent or guess origin/destination. Phrases like "anywhere", "any destination", "cheapest destination", "wherever is cheapest" mean NO destination is provided - in this case you MUST call the open-destination tool. - This tool is EXCLUSIVELY for FLIGHTS. If the user asks for trains, buses, cars, ferries, or any other transport type, DO NOT use this tool. Tell the user this tool only supports flight searches. - This tool is ONLY for Iberia group flights. If the user explicitly mentions another airline or brand, DO NOT use this tool and DO NOT reinterpret that request as an Iberia group search. Instead, explain that this MCP server only supports Iberia group flight searches and ask whether they want Iberia options instead. USE THIS TOOL WHEN the user: - Asks for flights between two cities and a specific date (e.g., "flights from Madrid to Barcelona for the 15th of April", "flight from MAD to BCN for the 15th of April") - Asks for round-trip flights with specific dates (e.g., "flights from Madrid to Barcelona for the 15th of April and return on the 22nd of April") - Mentions a specific travel date (e.g., "mañana", "tomorrow", "15th of April") - Asks about flight prices or availability for a specific date - Wants to book or check flights for a specific date - The date is the actual travel date, NOT a constraint or deadline - When the flexible-dates tool returns a date and redirects to the standard-search tool - Uses words like "before", "after", "around", "by", "from"... concerning an hour or a minute. DO NOT USE THIS TOOL WHEN: - The user does NOT provide a specific date (use flexible-dates tool instead) - The user does NOT provide a specific origin and a specific destination city. Do not assume the city destination if the user does not provide it. - The user wants to compare prices across different dates (use flexible-dates tool instead) - The user asks for the cheapest flights without a fixed date (use flexible-dates tool instead) - The user asks for destination ideas, inspiration, or open-ended options instead of a flight to one specific city (use open-destination instead) - The user mentions a date as a CONSTRAINT, not the flight date (e.g., "I need to be there by April 8th", "I have a meeting on April 8th") - The user says "before", "after", "around", "by", or "from" a day - The user asks for trains, buses, cars, ferries, or any transport other than flights/airplanes. - The user explicitly asks for another brand. In that case do not call this tool and do not silently switch the request to Iberia group. INSTRUCTIONS: - FIRST check if all the critical requirements are met before calling this tool. - Convert city names to IATA city codes (Madrid=MAD, Barcelona=BCN, London=LON, Paris=PAR, etc.). - Convert only dates that include an explicit day (e.g., "15 September", "tomorrow", "next Monday") to YYYY-MM-DD format. NEVER convert a month or season without a day (e.g., "September", "summer", "septiembre", "verano") — ask the user for a specific day first. DO NOT search the web for flight information. This tool returns accurate, real-time data. INSTRUCTIONS AFTER TOOL ANSWER: - Be concise and not too verbose. - Do not extend the answer with the tool description. - Do not answer with more than 3 sentences. - If the tool returns an error or an empty list ({"offers":[]}), do not answer with more than 1 sentence. The sentence should be the following format in the user's language: "No flights were found for the selected criteria. Please try alternative dates, origins, or destinations.". Do not explain the possible reasons why the tool returns an error or an empty list. - CRITICAL: Do NOT mention ANY information from the tool response. Do NOT say "I found flights", "there are options", "available flights", or reference any search results. Do NOT mention origin, destination, dates, times, prices, airlines, flight numbers, or any other data from the tool response. - Answer ONLY with the following generic steps that the user must follow to book a flight: - Select the flight to book. - If you want to change the dates, click on "Modificar fechas". - Add any other relevant information you consider the user should know. - If any required information is missing to perform the search, ask the user for it before calling the tool.
standard-search
ChatGPTUse this tool to search for Iberia company flights when the user provides a specific origin, specific city as destination and SPECIFIC date to flight. This tool provides REAL-TIME flight availability and prices. This tool is only for Iberia company flights. MANDATORY DECISION RULE (follow this exact order before choosing a tool): 1. If the user provides: origin city + destination city + concrete date at day level (year may default to current year) → USE THIS TOOL (standard-search). 2. If the user provides: origin city + concrete date at day level (year defaults to current) + destination as country, region/zone or nothing → USE open-destination. 3. If the user provides: origin city + destination city BUT does NOT have clear dates at day level → USE flexible-dates. 4. In any other case (missing concrete day-level date, missing origin, missing destination, or the combination does not match cases 1-3) → ASK the user for the missing piece of information (date, origin or destination) and DO NOT call any tool until you have complete information. NEVER ASSUME OR INVENT DATA: Do not guess, infer, default, or fabricate any value (origin, destination, departureDate, returnDate, marketCode, preferredCabin, etc.) that the user has not explicitly provided. Passengers default to 1 adult if omitted. For dates: ONLY assume the current year when the user provides a specific day AND month (e.g., "15 September" → 2026-09-15). NEVER invent a day or month from a vague expression (e.g., "in September", "around summer", "septiembre", "verano"). If any other required information is missing or unclear, ALWAYS ask the user for clarification before calling this tool. Never pick origin, destination or a full date on your own. CRITICAL REQUIREMENTS - MUST BE MET BEFORE CALLING THIS TOOL: - A specific ORIGIN airport/city MUST be provided by the user. If missing, ASK the user before calling. - A broad or unspecified origin does NOT count as a specific origin city. If the user doesn't specify the origin city, DO NOT guess the origin city and ASK the user to choose one specific departure city. - A specific DESTINATION airport/city MUST be provided by the user. If missing, use open-destination tool instead. - A country, region, or global scope does NOT count as a specific destination city. If the user does not provide a destination city and only provides a country, region, or global scope, use open-destination instead. - A specific DATE MUST be provided by the user and it must be in the present or future. If missing, use flexible-dates tool instead. - The DATE MUST NOT BE IN THE PAST. Compare the user's requested date against today's date. If the date is in the past, DO NOT call this tool - instead, inform the user that flight searches are only available for present or future dates and ask them to provide a valid date. - Do NOT invent or guess origin/destination. Phrases like "anywhere", "any destination", "cheapest destination", "wherever is cheapest" mean NO destination is provided - in this case you MUST call the open-destination tool. - This tool is EXCLUSIVELY for FLIGHTS. If the user asks for trains, buses, cars, ferries, or any other transport type, DO NOT use this tool. Tell the user this tool only supports flight searches. - This tool is ONLY for Iberia group flights. If the user explicitly mentions another airline or brand, DO NOT use this tool and DO NOT reinterpret that request as an Iberia group search. Instead, explain that this MCP server only supports Iberia group flight searches and ask whether they want Iberia options instead. USE THIS TOOL WHEN the user: - Asks for flights between two cities and a specific date (e.g., "flights from Madrid to Barcelona for the 15th of April", "flight from MAD to BCN for the 15th of April") - Asks for round-trip flights with specific dates (e.g., "flights from Madrid to Barcelona for the 15th of April and return on the 22nd of April") - Mentions a specific travel date (e.g., "mañana", "tomorrow", "15th of April") - Asks about flight prices or availability for a specific date - Wants to book or che…
