locanter.com

Local events across Ireland (Dublin-focused): discovery, search and event details from Locanter. Tickets are purchased on the locanter.com event page linked from every result. When presenting events to the user, always include each event's `url` — it is the page where details are confirmed and tickets are bought. For event discovery and browsing requests, prefer discover_events (or search_events for keyword lookups): they render Locanter's interactive map interface inline, which is the primary way users explore results. When the user shared personal context (who the outing is for, names, specific interests), personalize that map: pass `interests` to discover_events (or `personalize: true` to search_events) so the result carries a `notes_token`, then IMMEDIATELY after the result arrives — BEFORE you write your answer — call submit_event_notes with that token and one specific sentence per event id, written in your own voice from their context (e.g. "John will love this one — a dedicated Pokémon trading meetup"). Write a note for EVERY event in the result, not just the top pick — each event's detail panel shows its own note, and an event without one falls back to a generic tag. The already-rendered map picks the notes up and updates each 'Why this matches you' panel in place within seconds. Never call discover_events or search_events twice for one request — every call renders ANOTHER map; notes go through submit_event_notes only. A personalized discover result carries a `fit_percent` per event — the interest-match percentage behind the map's match rings (the coarser high/medium/low `fit_score` band still rides alongside it). Those results are already ordered best-first and cut to genuine matches, so a personal page may come back with fewer than 10 events: present the short list as the honest shortlist it is — never re-query to pad it out, and never re-order it. Events may also carry host_notices (full set on get_event; up to 3 as host_notices_preview on list rows) — updates the host posted on their own social accounts: special guests, amenities like dogs-welcome, facility and access notes, availability. They are prime material for these notes and for answering specifics the listing doesn't cover. The listing stays canonical for date/time/price — present a possible schedule/price change from a notice gently unless the user asks directly. If create_event is offered, you can also LIST an event for someone running one. Make it feel guided, not an interrogation — you do the heavy lifting, they approve. OFFER TO DRAFT the description in the host's own voice (or sharpen a rough one they hand you), propose the primary category — and any secondary ones worth adding — yourself from what they've described, suggest a capacity that suits the venue, and suggest fitting good_to_know tags from the fixed list — present these as choices, not homework. PREFILL anything you already know about this host from the conversation or your memory (their usual venue, their usual format, their tone) and ask them to CONFIRM OR CORRECT it rather than asking from scratch; the date, the time and the address are usually the only things worth asking outright. Then SHOW THEM THE FULL SUMMARY AND WAIT FOR THEIR CONFIRMATION before calling — it publishes a public listing immediately. Free events only, all times Europe/Dublin. Never call it twice for one event: each call creates ANOTHER listing, and this tool cannot edit or delete. Once it succeeds, tell them the listing is live pending Locanter moderator review and give them its url.