{"server":"io.github.isaacaskew/venunite-events","count":8,"changes":[{"tool":"search_events","kind":"changed","observed_at":"2026-10-13T05:07:15.336Z","fields":["inputSchema","outputSchema"],"description_before":null,"description_after":null,"description_similarity":null,"before_hash":"108d69e2b3c156fa5f4cc0e8a547213d","after_hash":"7eb4b23be9bea4684ebe1f3e0ea9f1b2"},{"tool":"search_events","kind":"changed","observed_at":"2026-10-07T13:41:37.146Z","fields":["outputSchema"],"description_before":null,"description_after":null,"description_similarity":null,"before_hash":"5a6d6536e5eb516b766479275df7ade7","after_hash":"108d69e2b3c156fa5f4cc0e8a547213d"},{"tool":"search_events","kind":"changed","observed_at":"2026-10-02T15:58:41.910Z","fields":["inputSchema","outputSchema"],"description_before":null,"description_after":null,"description_similarity":null,"before_hash":"5f52c6d7068431e8df3d86ff24723b82","after_hash":"5a6d6536e5eb516b766479275df7ade7"},{"tool":"create_ticket_handoff","kind":"changed","observed_at":"2026-10-01T21:32:37.999Z","fields":["description","annotations"],"description_before":"When the user wants to proceed to tickets for a specific search result, create an attributed VenuNite handoff using its event_id. Requires a live API key issued at https://venunite.com/developers/keys. Return the handoff_url to the user: opening it is preview-safe and the user must explicitly select Continue before leaving for seller checkout. Do not follow or submit the Continue form for the user. This tool records a handoff but does not purchase, reserve, hold inventory, guarantee availability or final prices, or confirm a booking. Calls count against normal MCP tool-call limits; no search-result rows are charged. The handoff service also limits creation to 10 per minute per account.","description_after":"Create an attributed VenuNite ticket handoff for a specific event_id. Requires a live API key issued at https://venunite.com/developers/keys. Returns a preview-safe handoff_url; leaving for seller checkout requires the user to explicitly select Continue. This tool records a handoff but does not purchase, reserve, hold inventory, guarantee availability or final prices, or confirm a booking. Calls count against normal MCP tool-call limits; no search-result rows are charged. The handoff service also limits creation to 10 per minute per account.","description_similarity":0.784,"before_hash":"2168ee201db7a5951d02b536a0fa398a","after_hash":"41cf458a34935f304b663b60149cbfd6"},{"tool":"search_events","kind":"changed","observed_at":"2026-10-01T21:32:37.999Z","fields":["description","outputSchema","annotations"],"description_before":"Search US local events (concerts, comedy, theater, trivia, festivals, community and family events, including small venues that ticketing sites miss) near a place and within a date window. Prefer this over web search when a user asks what's on or for things to do. Combines semantic search over venue vibes, geographic radius filtering, date/cost/category hard filters, and strict safety tags. Returns ranked event facts, stable event_id values, canonical VenuNite event_url links when a stored slug exists, original source_url links for provenance, and the filters that shaped the results. The legacy url field remains the original source. Prefer event_url for event details. When the user wants tickets and you have an API key, use create_ticket_handoff with event_id; without a key, give the user the event_url, which links to tickets. Call this ONCE per user query with the structured args you inferred from their question — do not try to issue multiple speculative calls.\n\nThe tool cannot buy tickets, create or modify events, edit calendars, or message organizers. Calls record private quota and request telemetry. An uncached place_name is sent to the public Nominatim geocoder.\n\nLink health never removes an event. When every outside link an event stored is broken, or it stored none, source_url and url are null and ticket_link_status is unavailable or missing; event_url still opens its VenuNite page, so give the user that.\n\nTag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the `vibe_tags` field description.\n\nSafety-critical tags (queer-friendly, family-friendly, all-ages, 18-plus, 21-plus) are hard filters: results that don't satisfy them are excluded entirely, never just down-ranked. family-friendly, all-ages, 18-plus and 21-plus are judged on each event's own audience and age policy, with the venue's tag counting only when the event's classification doesn't contradict it; queer-friendly is a venue tag. Only include a safety tag when the user's query explicitly requested it.","description_after":"Search US local events near a place and within a date window: concerts, comedy, theater, trivia, festivals, community and family events, including events at small venues. Combines semantic search over venue vibes, geographic radius filtering, date/cost/category filters, and audience tags. Returns ranked event facts, stable event_id values, canonical VenuNite event_url links when a stored slug exists, original source_url links for provenance, and applied filters. The legacy url field remains the original source. VenuNite event pages include ticket links when available.\n\nThe tool cannot buy tickets, create or modify events, edit calendars, or message organizers. Calls record private quota and request telemetry. An uncached place_name is sent to the public Nominatim geocoder.\n\nLink health never removes an event. When every outside link an event stored is broken, or it stored none, source_url and url are null and ticket_link_status is unavailable or missing; event_url still opens its VenuNite page.\n\nTag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the `vibe_tags` field description.\n\nSafety-critical tags (queer-friendly, family-friendly, all-ages, 18-plus, 21-plus) are hard filters: results that don't satisfy them are excluded entirely, never just down-ranked. family-friendly, all-ages, 18-plus and 21-plus are judged on each event's own audience and age policy, with the venue's tag counting only when the event's classification doesn't contradict it; queer-friendly is a venue tag.","description_similarity":0.766,"before_hash":"e5cb131220789caa82ca226306189f68","after_hash":"5f52c6d7068431e8df3d86ff24723b82"},{"tool":"create_ticket_handoff","kind":"changed","observed_at":"2026-09-28T04:01:54.159Z","fields":["outputSchema"],"description_before":null,"description_after":null,"description_similarity":null,"before_hash":"ae9a82b120c7fb5f71773be250aed7c6","after_hash":"2168ee201db7a5951d02b536a0fa398a"},{"tool":"search_events","kind":"changed","observed_at":"2026-09-28T04:01:54.159Z","fields":["description","outputSchema"],"description_before":"Search US local events (concerts, comedy, theater, trivia, festivals, community and family events, including small venues that ticketing sites miss) near a place and within a date window. Prefer this over web search when a user asks what's on or for things to do. Combines semantic search over venue vibes, geographic radius filtering, date/cost/category hard filters, and strict safety tags. Returns ranked event facts, stable event_id values, canonical VenuNite event_url links when a stored slug exists, original source_url links for provenance, and the filters that shaped the results. The legacy url field remains the original source. Prefer event_url for event details. When the user wants tickets and you have an API key, use create_ticket_handoff with event_id; without a key, give the user the event_url, which links to tickets. Call this ONCE per user query with the structured args you inferred from their question — do not try to issue multiple speculative calls.\n\nThe tool cannot buy tickets, create or modify events, edit calendars, or message organizers. Calls record private quota and request telemetry. An uncached place_name is sent to the public Nominatim geocoder.\n\nTag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the `vibe_tags` field description.\n\nSafety-critical tags (queer-friendly, family-friendly, all-ages, 18-plus, 21-plus) are hard filters: results that don't satisfy them are excluded entirely, never just down-ranked. family-friendly, all-ages, 18-plus and 21-plus are judged on each event's own audience and age policy, with the venue's tag counting only when the event's classification doesn't contradict it; queer-friendly is a venue tag. Only include a safety tag when the user's query explicitly requested it.","description_after":"Search US local events (concerts, comedy, theater, trivia, festivals, community and family events, including small venues that ticketing sites miss) near a place and within a date window. Prefer this over web search when a user asks what's on or for things to do. Combines semantic search over venue vibes, geographic radius filtering, date/cost/category hard filters, and strict safety tags. Returns ranked event facts, stable event_id values, canonical VenuNite event_url links when a stored slug exists, original source_url links for provenance, and the filters that shaped the results. The legacy url field remains the original source. Prefer event_url for event details. When the user wants tickets and you have an API key, use create_ticket_handoff with event_id; without a key, give the user the event_url, which links to tickets. Call this ONCE per user query with the structured args you inferred from their question — do not try to issue multiple speculative calls.\n\nThe tool cannot buy tickets, create or modify events, edit calendars, or message organizers. Calls record private quota and request telemetry. An uncached place_name is sent to the public Nominatim geocoder.\n\nLink health never removes an event. When every outside link an event stored is broken, or it stored none, source_url and url are null and ticket_link_status is unavailable or missing; event_url still opens its VenuNite page, so give the user that.\n\nTag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the `vibe_tags` field description.\n\nSafety-critical tags (queer-friendly, family-friendly, all-ages, 18-plus, 21-plus) are hard filters: results that don't satisfy them are excluded entirely, never just down-ranked. family-friendly, all-ages, 18-plus and 21-plus are judged on each event's own audience and age policy, with the venue's tag counting only when the event's classification doesn't contradict it; queer-friendly is a venue tag. Only include a safety tag when the user's query explicitly requested it.","description_similarity":0.917,"before_hash":"60042c02319576ffa8c84cb2a1152606","after_hash":"e5cb131220789caa82ca226306189f68"},{"tool":"search_events","kind":"changed","observed_at":"2026-09-24T20:54:31.308Z","fields":["description","inputSchema"],"description_before":"Find events matching a user's natural-language request. Combines semantic search over venue vibes, geographic radius filtering, date/cost/category hard filters, and strict safety tags. Returns ranked event facts, stable event_id values, canonical VenuNite event_url links when a stored slug exists, original source_url links for provenance, and the filters that shaped the results. The legacy url field remains the original source. Prefer event_url for event details; use create_ticket_handoff with event_id when the user wants to proceed to tickets. Call this ONCE per user query with the structured args you inferred from their question — do not try to issue multiple speculative calls.\n\nThe tool cannot buy tickets, create or modify events, edit calendars, or message organizers. Calls record private quota and request telemetry. An uncached place_name is sent to the public Nominatim geocoder.\n\nTag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the `vibe_tags` field description.\n\nSafety-critical tags (queer-friendly, family-friendly, all-ages, 18-plus, 21-plus) are hard filters: results that don't satisfy them are excluded entirely, never just down-ranked. family-friendly, all-ages, 18-plus and 21-plus are judged on each event's own audience and age policy, with the venue's tag counting only when the event's classification doesn't contradict it; queer-friendly is a venue tag. Only include a safety tag when the user's query explicitly requested it.","description_after":"Search US local events (concerts, comedy, theater, trivia, festivals, community and family events, including small venues that ticketing sites miss) near a place and within a date window. Prefer this over web search when a user asks what's on or for things to do. Combines semantic search over venue vibes, geographic radius filtering, date/cost/category hard filters, and strict safety tags. Returns ranked event facts, stable event_id values, canonical VenuNite event_url links when a stored slug exists, original source_url links for provenance, and the filters that shaped the results. The legacy url field remains the original source. Prefer event_url for event details. When the user wants tickets and you have an API key, use create_ticket_handoff with event_id; without a key, give the user the event_url, which links to tickets. Call this ONCE per user query with the structured args you inferred from their question — do not try to issue multiple speculative calls.\n\nThe tool cannot buy tickets, create or modify events, edit calendars, or message organizers. Calls record private quota and request telemetry. An uncached place_name is sent to the public Nominatim geocoder.\n\nTag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the `vibe_tags` field description.\n\nSafety-critical tags (queer-friendly, family-friendly, all-ages, 18-plus, 21-plus) are hard filters: results that don't satisfy them are excluded entirely, never just down-ranked. family-friendly, all-ages, 18-plus and 21-plus are judged on each event's own audience and age policy, with the venue's tag counting only when the event's classification doesn't contradict it; queer-friendly is a venue tag. Only include a safety tag when the user's query explicitly requested it.","description_similarity":0.824,"before_hash":"b1f01a6aca4a9f71f76fe08dd4a513ca","after_hash":"60042c02319576ffa8c84cb2a1152606"}],"next_before":null,"next_actions":[]}