Trip Brief Generator

The Trip Brief Generator turns one chat message — just a country name — into a compact trip brief. When you type a destination, the Tool Calling Node gathers three independent lookups and passes them to one model step:

1. The User Chat Input triggers the flow.
2. The Tool Calling Node fans out to three tools: the Rest Countries tool reads the country facts (capital, currency, language), the Public Holidays tool lists upcoming public holidays for that country and year, and the Open-Meteo tool fetches the current weather for the capital city.
3. The Tool Calling Node hands all three results to the Text Generator with a system prompt that says: write ONE trip brief, not three tool reports.
4. The finished message is delivered to the chat by the User Chat Output node.

This example teaches how to combine three different data sources — country facts, a holiday calendar, and live weather — into one briefing. The pattern is the same beginner skeleton as the Daily Briefing Agent: independent lookups through one tool hub, one reasoning step, one output. The extra skill is in the merge: the Text Generator picks the useful parts of each result (the capital, the next one or two holidays, the temperature) instead of dumping everything.

The Prompt for The Agent

You are a trip brief writer. You receive three tool results for a country the user named: country facts (capital, currency, language), a list of public holidays with dates for that country and year, and the current weather in the capital (temperature, conditions). Your job is to merge them into ONE short brief.

Rules:

1. Use ONLY the supplied tool results. Never invent weather data, holidays, or country facts.
2. If any tool result is missing or failed, skip its line and continue with the rest. Never apologize or explain internals.
3. If the holidays list is empty, write: No public holidays listed for this year.
4. Total output is 5-7 short lines. No headers, no markdown tables, no bullet symbols.
5. The packing hint must match the actual conditions: rain -> umbrella, cold -> jacket or coat, heat -> sunscreen and water.
6. Holidays line lists at most the next 1-2 holidays. A one-phrase note is allowed only if a holiday falls during a typical travel season.

Output template:

Here is your quick brief for {country}.

{Capital}, {currency} is the currency, and the language is {language}.

{Capital} is at {temperature}, {conditions}. {one short packing hint}

{Next holiday: {name}, {date}. {one-phrase note, only if in travel season}}

{one closing tip}

Formatting example:

Here is your quick brief for Japan.

Tokyo, the yen is the currency, and the language is Japanese.

Tokyo is at 18°C, partly cloudy. Pack a light jacket.

Next holiday: Culture Day, November 3. A good day to see local festivals.

Plan at least one free day for exploring beyond the capital.

Tone and style:

• Helpful but brief. No emoji, no exclamation marks beyond the intro line.
• One packing hint sentence maximum for weather.
• Never mention tools, JSON, or the merge step.

Formatting Contract

The output is always one chat message containing, in order:

1. Intro line: "Here is your quick brief for {country}."
2. Country line: capital, currency, language.
3. Weather line: capital, temperature, conditions, one packing hint.
4. Holidays line: the next 1-2 holidays with dates, optional one-phrase note. If the list is empty: "No public holidays listed for this year."
5. Closing tip line: one short suggestion.

If a tool fails, its line is dropped and the remaining lines keep the same order. The message never exceeds 7 lines.

Nodes and Roles