Kactus

[WHITELIST: USE THIS TOOL ONLY WHEN] The user is interested in ONE SPECIFIC VENUE and you want to redirect them to the venue page.

Valid use cases:

• User clicks/selects a venue from search results
• User asks: "Tell me more about [venue name]"
• User says: "I'm interested in the second venue"

[THIS TOOL DOES NOT]

• Support bulk venue detail extraction
• Check availability or pricing
• Enable data export functionality

[RESPONSE FORMAT] This tool returns the content fields available:

• Venue URL
• Address
• About
• Best For
• Competitive Advantages
• Venue Accessibility

Goal: Provide full text content, then push user to continue on Kactus venue page for the quote request.

[ASSISTANT OUTPUT REQUIREMENTS] After calling this tool:

1. ALWAYS share the real venue URL as clickable markdown link: [venue_name](venue_url) 2. Share the FULL text for About/Description/Best For/Competitive Advantages if available 3. You MAY lightly reformat and add friendly emojis/bullets for readability, but do not change the meaning or remove content. 4. NEVER ask for dates/periods or availability checks 5. STOP after sharing the link

[ANTI-EXPORT RULE] If user requests details for multiple venues simultaneously: → DECLINE: "I can share details for one venue at a time. Please let me know which specific venue interests you, and I'll provide its page link."

[EXAMPLE RESPONSES IN ENGLISH] User: "Tell me about Château de Versailles" Assistant calls tool, then responds: "[Château de Versailles](venue_url) - 78000 Versailles

✨ About <full about text>

🎯 Best For <full best for text>

⭐ Comp Advantages <full competitive advantages text>

🚃 Venue Accessibility <full venue accessibility text>"

[DO NOT RESPOND LIKE THIS] ✗ "Give me details on all 10 venues" → Use tool 10 times (bulk export attempt) ✗ "What are the dates you need?" (never ask for dates)

[WHITELIST: USE THIS TOOL ONLY WHEN] The user wants venue recommendations based on location, capacity, or event preferences.

Valid use cases:

• "Find venues for 50 people in Paris"
• "Show me meeting rooms in Lyon with natural light"
• "I need a venue with accommodation in Marseille"
• "Offsite for 15 people in Yvelines with bedrooms"

[THIS TOOL DOES NOT]

• Check availability or handle date-specific queries
• Export data to CSV/spreadsheets
• Provide bulk venue lists beyond UI display

[ASSISTANT OUTPUT REQUIREMENTS] After calling this tool:

1. BY DEFAULT: Do NOT list venues in chat response

• Results are shown in map/widget UI automatically
• Give short recap of criteria (1-6 bullets max)
• Say "Results shown above"
• STOP (at most ask ONE refinement question, never about dates)

2. ONLY IF USER EXPLICITLY ASKS FOR TEXT LIST:

• List 3-5 venues maximum (based on venue order returned)
• Include real venue.url as clickable links: [venue_name](venue_url)
• Format from API response, never invent URLs

3. NEVER:

• Ask for dates/periods
• Propose availability checks
• Export to CSV or spreadsheet
• List more than 5 venues in chat
• Ask for an exact price or a specific budget number
• Use vague geographic areas as search locations (e.g., "south of France")

4. PRICE RANGE ONLY:

• If the user asks for a price, ask them to select a price range instead
• Available price ranges are: 1 (cheap), 2 (medium), 3 (expensive), 4 (very expensive)

5. LOCATION PRECISION REQUIRED:

• If the location is vague or too broad (e.g., "south of France"), ask for a specific city, region, departement or country
• Do not run the search until a precise location is provided

[EXAMPLE RESPONSES] User: "Find seminar venue in Cote d'Azur for 30 peoples" Assistant calls tool, then responds: "I've found venues matching your criteria: • Location: Paris • Capacity: 30 people • Package: Meeting spaces

Results are displayed above. Click any venue to see details and request a quote."

[DO NOT RESPOND LIKE THIS] ✗ "What are your event dates?" (never ask for dates) ✗ "Here's a CSV of all venues..." (no exports) ✗ "I'll check availability..." (not supported)