Local US events: trivia, libraries, markets and gigs, with VenuNite links and ticket handoffs.
Scored across 2 tools
The two tools have clearly distinct purposes: one searches events, the other creates a ticket handoff for a specific event_id. There is no overlap in function, and an agent can easily select the right tool.
Both names follow a consistent verb_noun snake_case pattern: search_events and create_ticket_handoff. The convention is predictable and readable.
Two tools is borderline thin for an events platform that includes search and handoff functionality. While the scope may be intentionally narrow, the set feels underpowered compared to typical MCP servers in this domain.
The surface covers event discovery and handoff creation, but lacks operations like fetching a single event by ID, listing canonical tags, or managing/canceling handoffs. These are notable gaps that could cause agents to hit dead ends.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | The stable VenuNite event_id returned by search_events. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the annotations by disclosing the API-key auth requirement, the 10-per-minute per-account rate limit, the billing behavior (counts against tool-call limits, no search-result charges), and the exact side-effect boundary (no purchase, reserve, hold, availability guarantee, or booking confirmation). This is precisely the extra context annotations cannot carry.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the core action and resource, then layers auth, return value, side-effect disclaimer, and limits in tight sentences. Every sentence carries distinct information; nothing is redundant with the name or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not explain return values, yet it still flags handoff_url as preview-safe. Auth, rate limits, billing, and side-effect boundaries are all covered, leaving no gap an agent needs before calling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and event_id is fully documented in the schema as the stable ID returned by search_events. The description only echoes that it must be a 'specific event_id', adding no format or constraint detail beyond the structured field, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (create) and resource (attributed VenuNite ticket handoff) scoped to an event_id. The reader can immediately separate it from the sibling search_events, which only retrieves events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives clear preconditions (live API key, user must explicitly select Continue) and a firm scope boundary (records a handoff, does not purchase/reserve/hold/confirm). It never explicitly names search_events as the alternative or states when not to call it, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
The 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.
Link 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.
Tag vocabulary is fixed (49 canonical tags across 6 facets: ambiance, social, time, age, venue_type, activity). See the vibe_tags field description.
Safety-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.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Ordering axis. Results are presented by calendar day in timezone; sort orders within each day. With query_text, the server selects the strongest event-text and venue-vibe matches under every sort, and sort only orders them. Without query_text, the result limit is shared across the days of the window: events starting inside it come before events already under way, and each day contributes its next event on the sort axis. | |
| limit | No | Number of events to return. Default 20. Prefer small (5-10) when the user asked for a single recommendation. | |
| date_end | No | Exclusive ISO-8601 end of the search window, including the local UTC offset. Default: 14 days from date_start. The words now, today, tonight, tomorrow and this weekend are also accepted and resolved in the caller's timezone. 'Tonight' → date_start + 6 hours. 'Next weekend' → date_start + 2 days. An event starting exactly at date_end is outside this window. | |
| max_cost | No | Upper bound on event cost in USD. 'cheap' ≈ 15, 'affordable' ≈ 30, 'under $X' → X. Events with no listed price stay in the results (most events list none), so present their price as unverified rather than excluding them. max_cost=0 returns only proven-free events. Leave unset if the user didn't constrain price. | |
| min_cost | No | Lower bound on event cost. Rarely useful — only set when the user explicitly excluded free events. | |
| timezone | No | IANA timezone (e.g. 'America/New_York') used for the calendar-day grouping of results. Default UTC — pass the user's local zone so 'today/tomorrow' day buckets match their clock. | UTC |
| vibe_tags | No | Canonical vibe vocabulary. Include tags the user explicitly or strongly implied. IMPORTANT: the tags `queer-friendly`, `family-friendly`, `all-ages`, `18-plus`, `21-plus` are HARD filters — only include them when the user's query explicitly asked for that property. Including `family-friendly` for a user who just said 'something fun tonight' will exclude most events. | |
| categories | No | Event category(s). Map the user's intent: 'live music' → music, 'standup' → comedy, 'trivia night' → trivia-games, 'art opening' → arts-culture. 'anything to do' → omit (no category filter). | |
| center_lat | No | Latitude (only if you already have precise coordinates — otherwise pass place_name). | |
| center_lng | No | Longitude (paired with center_lat). | |
| date_match | No | overlap includes events already running during the window, such as multi-day festivals or prior-night shows; events ending exactly at date_start are excluded. starts_within requires the event to start at or after date_start and before date_end. Prefer starts_within for requests about events starting tomorrow, on a specified date, this evening, or this weekend. Keep overlap when the user asks what is currently happening or wants ongoing activities. | overlap |
| date_start | No | Inclusive ISO-8601 start of the search window, including the local UTC offset. Default: now. The words now, today, tonight, tomorrow and this weekend are also accepted and resolved in the caller's timezone. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight. The timezone field controls day grouping, not parsing: date-times without an offset are interpreted as UTC. Use date_match=starts_within when the user wants events starting on a particular date or evening. | |
| local_only | No | Set true when the user's query implies 'in my immediate area' — 'what's on my block', 'nearby tonight', 'close by'. The server clamps the effective radius to a neighborhood-scale max based on local density (≤10mi urban, ≤30mi suburban, ≤50mi rural), even if radius_miles is larger. Prefer this over guessing a small radius — the server knows the density of the area and you don't. | |
| place_name | No | Human-readable location if the user mentioned one: 'Westminster, CO' or 'Five Points Denver'. Prefer this over guessed lat/lng when you have a name; existing precise coordinates take precedence. Always include the state abbrev when the city name is ambiguous. An unresolved place returns location_unresolved; correct the place or use known coordinates rather than dropping the location. | |
| query_text | No | Free-text vibe description extracted from the user's query. Keep it short — e.g. 'chill jazz' or 'loud rock club'. Omit when the user's request is purely geographic / tag-based (e.g. 'any comedy shows tonight near me'). | |
| state_hint | No | Two-letter state abbreviation to disambiguate place_name (e.g. place_name 'Frederick' + state_hint 'MD'). Unnecessary when place_name already contains the state. | |
| radius_miles | No | Search radius in miles. OMIT this field to let the server pick a density-aware default: 5mi in dense metros (Chicago, NYC), 15mi suburban, 25mi rural. Only pass an explicit value when the user's phrasing implies a specific scope: - 'walking distance' / 'on my block' → 2-3 - 'near me' in a dense downtown or neighborhood → 5-7 - 'near me' in a suburb → 10-15 - 'metro area' / 'anywhere in <city>' → 25-30 - rural 'near me' or 'within driving distance' → 25-50 For a user who says 'things to do tonight' in Lincolnwood, Chicago, or any other dense-urban location: omit this field. Passing 15 there pulls events from 8-10 miles away in other neighborhoods, which is worse than the density-aware default. Range 0.5 to 500. An out-of-range value FAILS the entire call and returns zero events — it is not clamped — so omit the field rather than guessing. Use 'local_only: true' instead of a small radius when you're unsure of local density. | |
| max_events_per_venue | No | Per-venue diversity cap. Default 1 — each venue contributes at most one event, giving a diverse 'what's on' feed. Raise to 3-5 for 'what's on at <specific venue>' queries where the user expects multiple shows from the same room. | |
| include_unknown_prices | No | Include events whose admission price cannot be determined. Default true preserves broad discovery; positive price bounds may then include unknown prices, which must be labeled unverified. false keeps only events with a listed price; most events list none, so it can empty an answer, and 'under $X' alone is not a reason to set it. When it leaves three or fewer results, applied_filters.available_if_relaxed reports how many the same search returns with unknown prices included. This never relaxes the proven-free requirement of max_cost=0. |
| Name | Required | Description |
|---|---|---|
| error | No | |
| results | Yes | |
| applied_filters | No | |
| validation_errors | No |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
search_events8 fields changedInput schema / properties / include_unknown_prices / descriptionPrevious value: -"Include events whose admission price cannot be determined. Default true preserves broad discovery; positive price bounds may then include unknown prices, which must be labeled unverified. Set false with min_cost/max_cost when the user explicitly requires a verified budget. This never relaxes the proven-free requirement of max_cost=0."New value: +"Include events whose admission price cannot be determined. Default true preserves broad discovery; positive price bounds may then include unknown prices, which must be labeled unverified. false keeps only events with a listed price; most events list none, so it can empty an answer, and 'under $X' alone is not a reason to set it. When it leaves three or fewer results, applied_filters.available_if_relaxed reports how many the same search returns with unknown prices included. This never relaxes the proven-free requirement of max_cost=0."Input schema / properties / max_cost / descriptionPrevious value: -"Upper bound on event cost in USD. 'cheap' ≈ 15, 'affordable' ≈ 30, 'under $X' → X. Set include_unknown_prices=false when the user explicitly wants a verified budget such as 'under $100'. max_cost=0 returns only proven-free events. Leave unset if the user didn't constrain price."New value: +"Upper bound on event cost in USD. 'cheap' ≈ 15, 'affordable' ≈ 30, 'under $X' → X. Events with no listed price stay in the results (most events list none), so present their price as unverified rather than excluding them. max_cost=0 returns only proven-free events. Leave unset if the user didn't constrain price."Input schema / properties / sort / descriptionPrevious value: -"Ordering axis. Results are presented by calendar day in timezone; sort orders within each day. With query_text and no explicit sort (or relevance), the server selects the strongest event-text and venue-vibe matches before applying that day order. Explicit date, distance, or demand sorts select by day and that axis. Without query_text, default date is chronological."New value: +"Ordering axis. Results are presented by calendar day in timezone; sort orders within each day. With query_text, the server selects the strongest event-text and venue-vibe matches under every sort, and sort only orders them. Without query_text, the result limit is shared across the days of the window: events starting inside it come before events already under way, and each day contributes its next event on the sort axis."Output schema / properties / applied_filters / properties / available_if_relaxedAdded value: +{
+ "description": "Present only when three or fewer results matched and a strict filter is why: how many results the same search returns, up to limit, without the strict tags or with unknown prices included. No relaxed result is returned.",
+ "properties": {
+ "with_unknown_prices": {
+ "type": "integer"
+ },
+ "without_strict_tags": {
+ "type": "integer"
+ }
+ },
+ "type": "object"
+}Output schema / properties / applied_filters / properties / filter_noteAdded value: +{
+ "description": "Present with available_if_relaxed; says the same in a sentence.",
+ "type": "string"
+}Output schema / properties / applied_filters / properties / text_match_noteAdded value: +{
+ "description": "Present only when query_text matched no returned event's own text. Says the results are venue-similarity matches that may be unrelated to the topic.",
+ "type": "string"
+}Output schema / properties / applied_filters / properties / text_matched_resultsAdded value: +{
+ "description": "Present only with query_text. How many of these results matched the query words in the event's own title or description; the others were chosen by venue similarity.",
+ "type": "integer"
+}Output schema / properties / results / items / properties / event_url / descriptionPrevious value: -"Canonical VenuNite event page; null when no stored slug exists."New value: +"Canonical VenuNite event page, tagged utm_source=mcp so the visit can be counted; null when no stored slug exists."search_events1 field changedOutput schema / properties / applied_filters / properties / horizon_noteAdded value: +{
+ "description": "Present only when the plan's lookahead cut the requested date window. Says what was asked for and what was searched; results stop at horizon_end.",
+ "type": "string"
+}search_events12 fields changedInput schema / properties / categories / maxItemsAdded value: +10Input schema / properties / center_lat / maximumAdded value: +90Input schema / properties / center_lat / minimumAdded value: +-90Input schema / properties / center_lng / maximumAdded value: +180Input schema / properties / center_lng / minimumAdded value: +-180Input schema / properties / max_cost / minimumAdded value: +0Input schema / properties / min_cost / minimumAdded value: +0Input schema / properties / query_text / maxLengthAdded value: +500Input schema / properties / timezone / defaultAdded value: +"UTC"Input schema / properties / vibe_tags / maxItemsAdded value: +12Output schema / properties / applied_filters / properties / contract_versionAdded value: +{
+ "description": "Version of the resolved search intent contract.",
+ "type": "integer"
+}Output schema / properties / applied_filters / properties / timezoneAdded value: +{
+ "description": "IANA timezone used for calendar-day grouping.",
+ "type": "string"
+}search_events2 fields changedOutput schema / properties / results / items / properties / event_id / descriptionPrevious value: -"Stable VenuNite identity; use this value with create_ticket_handoff."New value: +"Stable VenuNite event identity."Output schema / properties / results / items / properties / event_url / descriptionPrevious value: -"Canonical VenuNite event page; null when no stored slug exists. Prefer this link for event details."New value: +"Canonical VenuNite event page; null when no stored slug exists."create_ticket_handoff1 field changedOutput schema / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "booking_mode": {
- "const": "external_checkout"
- },
- "event_id": {
- "maximum": 2147483647,
- "minimum": 1,
- "type": "integer"
- },
- "event_url": {
- "format": "uri",
- "pattern": "^https://venunite\\.com/events/[^/?#]+$",
- "type": "string"
- },
- "expires_at": {
- "format": "date-time",
- "type": "string"
- },
- "handoff_id": {
- "maxLength": 128,
- "minLength": 1,
- "type": "string"
- },
- "handoff_url": {
- "format": "uri",
- "pattern": "^https://venunite\\.com/tickets/handoff/[A-Za-z0-9_-]{43}$",
- "type": "string"
- },
- "requires_user_action": {
- "const": true
- }
- },
- "required": [
- "handoff_id",
- "event_id",
- "event_url",
- "handoff_url",
- "expires_at",
- "booking_mode",
- "requires_user_action"
- ]
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "type": "string"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "error",
- "message"
- ]
- }
-]New value: +[
+ {
+ "properties": {
+ "booking_mode": {
+ "const": "external_checkout"
+ },
+ "event_id": {
+ "maximum": 2147483647,
+ "minimum": 1,
+ "type": "integer"
+ },
+ "event_url": {
+ "format": "uri",
+ "pattern": "^https://venunite\\.com/events/[^/?#]+$",
+ "type": "string"
+ },
+ "expires_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "handoff_id": {
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+ },
+ "handoff_url": {
+ "format": "uri",
+ "pattern": "^https://venunite\\.com/tickets/handoff/[A-Za-z0-9_-]{43}$",
+ "type": "string"
+ },
+ "requires_user_action": {
+ "const": true
+ }
+ },
+ "required": [
+ "handoff_id",
+ "event_id",
+ "event_url",
+ "handoff_url",
+ "expires_at",
+ "booking_mode",
+ "requires_user_action"
+ ]
+ },
+ {
+ "properties": {
+ "error": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "error",
+ "message"
+ ]
+ }
+]search_events5 fields changedOutput schema / additionalPropertiesRemoved value: -falseOutput schema / properties / applied_filters / additionalPropertiesRemoved value: -falseOutput schema / properties / results / items / additionalPropertiesRemoved value: -falseOutput schema / properties / results / items / properties / venue / additionalPropertiesRemoved value: -falseOutput schema / properties / validation_errors / items / additionalPropertiesRemoved value: -falsesearch_events2 fields changedOutput schema / properties / results / items / properties / source_url / descriptionPrevious value: -"Original event source for provenance. The legacy url field retains the same meaning."New value: +"Original event source for provenance; a link recorded as broken is replaced by its recorded replacement or returned as null. The legacy url field retains the same meaning."Output schema / properties / results / items / properties / ticket_link_statusAdded value: +{
+ "description": "available when a safe ticket or event destination can be served; unavailable when the event's stored links are all unusable; missing when none were supplied. The event is returned in every case.",
+ "enum": [
+ "available",
+ "unavailable",
+ "missing"
+ ],
+ "type": "string"
+}search_events3 fields changedInput schema / properties / date_end / descriptionPrevious value: -"Exclusive ISO-8601 end of the search window, including the local UTC offset. Default: 14 days from date_start. 'Tonight' → date_start + 6 hours. 'Next weekend' → date_start + 2 days. An event starting exactly at date_end is outside this window."New value: +"Exclusive ISO-8601 end of the search window, including the local UTC offset. Default: 14 days from date_start. The words now, today, tonight, tomorrow and this weekend are also accepted and resolved in the caller's timezone. 'Tonight' → date_start + 6 hours. 'Next weekend' → date_start + 2 days. An event starting exactly at date_end is outside this window."Input schema / properties / date_start / descriptionPrevious value: -"Inclusive ISO-8601 start of the search window, including the local UTC offset. Default: now. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight. The timezone field controls day grouping, not parsing: date-times without an offset are interpreted as UTC. Use date_match=starts_within when the user wants events starting on a particular date or evening."New value: +"Inclusive ISO-8601 start of the search window, including the local UTC offset. Default: now. The words now, today, tonight, tomorrow and this weekend are also accepted and resolved in the caller's timezone. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight. The timezone field controls day grouping, not parsing: date-times without an offset are interpreted as UTC. Use date_match=starts_within when the user wants events starting on a particular date or evening."Input schema / properties / radius_miles / defaultRemoved value: -nullcreate_ticket_handoffsearch_events3 fields changedOutput schema / properties / results / items / properties / event_idAdded value: +{
+ "description": "Stable VenuNite identity; use this value with create_ticket_handoff.",
+ "type": "integer"
+}Output schema / properties / results / items / properties / event_urlAdded value: +{
+ "description": "Canonical VenuNite event page; null when no stored slug exists. Prefer this link for event details.",
+ "format": "uri",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / results / items / properties / source_urlAdded value: +{
+ "description": "Original event source for provenance. The legacy url field retains the same meaning.",
+ "format": "uri",
+ "type": [
+ "string",
+ "null"
+ ]
+}search_events1 field changedInput schema / properties / vibe_tags / descriptionPrevious value: -"Canonical vibe vocabulary. Include tags the user explicitly or strongly implied. IMPORTANT: the tags `queer-friendly`, `family-friendly`, `all-ages`, `18-plus`, `21-plus` are HARD filters — only include them when the user's query explicitly asked for that property. Including `family-friendly` for a user who just said 'something fun tonight' will exclude most venues."New value: +"Canonical vibe vocabulary. Include tags the user explicitly or strongly implied. IMPORTANT: the tags `queer-friendly`, `family-friendly`, `all-ages`, `18-plus`, `21-plus` are HARD filters — only include them when the user's query explicitly asked for that property. Including `family-friendly` for a user who just said 'something fun tonight' will exclude most events."search_events3 fields changedInput schema / properties / radius_miles / descriptionPrevious value: -"Search radius in miles. OMIT this field to let the server pick a density-aware default: 5mi in dense metros (Chicago, NYC), 15mi suburban, 25mi rural. Only pass an explicit value when the user's phrasing implies a specific scope:\n - 'walking distance' / 'on my block' → 2-3\n - 'near me' in a dense downtown or neighborhood → 5-7\n - 'near me' in a suburb → 10-15\n - 'metro area' / 'anywhere in <city>' → 25-30\n - rural 'near me' or 'within driving distance' → 25-50\n\nFor a user who says 'things to do tonight' in Lincolnwood, Chicago, or any other dense-urban location: omit this field. Passing 15 there pulls events from 8-10 miles away in other neighborhoods, which is worse than the density-aware default.\n\nMax 500. Use 'local_only: true' instead of a small radius when you're unsure of local density."New value: +"Search radius in miles. OMIT this field to let the server pick a density-aware default: 5mi in dense metros (Chicago, NYC), 15mi suburban, 25mi rural. Only pass an explicit value when the user's phrasing implies a specific scope:\n - 'walking distance' / 'on my block' → 2-3\n - 'near me' in a dense downtown or neighborhood → 5-7\n - 'near me' in a suburb → 10-15\n - 'metro area' / 'anywhere in <city>' → 25-30\n - rural 'near me' or 'within driving distance' → 25-50\n\nFor a user who says 'things to do tonight' in Lincolnwood, Chicago, or any other dense-urban location: omit this field. Passing 15 there pulls events from 8-10 miles away in other neighborhoods, which is worse than the density-aware default.\n\nRange 0.5 to 500. An out-of-range value FAILS the entire call and returns zero events — it is not clamped — so omit the field rather than guessing. Use 'local_only: true' instead of a small radius when you're unsure of local density."Input schema / properties / radius_miles / maximumAdded value: +500Input schema / properties / radius_miles / minimumAdded value: +0.5search_events3 fields changedOutput schema / properties / applied_filters / properties / horizon_endAdded value: +{
+ "format": "date-time",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / applied_filters / properties / policy_versionAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / applied_filters / properties / requested_limitAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}search_events8 fields changedInput schema / properties / date_end / descriptionPrevious value: -"ISO-8601 end of the search window. Default: 14 days from date_start. 'Tonight' → date_start + 6 hours. 'Next weekend' → date_start + 2 days."New value: +"Exclusive ISO-8601 end of the search window, including the local UTC offset. Default: 14 days from date_start. 'Tonight' → date_start + 6 hours. 'Next weekend' → date_start + 2 days. An event starting exactly at date_end is outside this window."Input schema / properties / date_matchAdded value: +{
+ "default": "overlap",
+ "description": "overlap includes events already running during the window, such as multi-day festivals or prior-night shows; events ending exactly at date_start are excluded. starts_within requires the event to start at or after date_start and before date_end. Prefer starts_within for requests about events starting tomorrow, on a specified date, this evening, or this weekend. Keep overlap when the user asks what is currently happening or wants ongoing activities.",
+ "enum": [
+ "overlap",
+ "starts_within"
+ ],
+ "type": "string"
+}Input schema / properties / date_start / descriptionPrevious value: -"ISO-8601 start of the search window. Default: now. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight. NOTE: the window matches by OVERLAP — an event that STARTED before date_start but is still running during the window (multi-day festival, a show that ends after midnight) is included. Filter client-side on `start` if you strictly need events that begin inside the window."New value: +"Inclusive ISO-8601 start of the search window, including the local UTC offset. Default: now. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight. The timezone field controls day grouping, not parsing: date-times without an offset are interpreted as UTC. Use date_match=starts_within when the user wants events starting on a particular date or evening."Input schema / properties / include_unknown_pricesAdded value: +{
+ "default": true,
+ "description": "Include events whose admission price cannot be determined. Default true preserves broad discovery; positive price bounds may then include unknown prices, which must be labeled unverified. Set false with min_cost/max_cost when the user explicitly requires a verified budget. This never relaxes the proven-free requirement of max_cost=0.",
+ "type": "boolean"
+}Input schema / properties / max_cost / descriptionPrevious value: -"Upper bound on event cost in USD. 'cheap' ≈ 15, 'affordable' ≈ 30, 'under $X' → X. Leave unset if the user didn't constrain price."New value: +"Upper bound on event cost in USD. 'cheap' ≈ 15, 'affordable' ≈ 30, 'under $X' → X. Set include_unknown_prices=false when the user explicitly wants a verified budget such as 'under $100'. max_cost=0 returns only proven-free events. Leave unset if the user didn't constrain price."Input schema / properties / place_name / descriptionPrevious value: -"Human-readable location if the user mentioned one: 'Westminster, CO' or 'Five Points Denver'. Prefer this over lat/lng when you have a name. Always include the state abbrev when the city name is ambiguous."New value: +"Human-readable location if the user mentioned one: 'Westminster, CO' or 'Five Points Denver'. Prefer this over guessed lat/lng when you have a name; existing precise coordinates take precedence. Always include the state abbrev when the city name is ambiguous. An unresolved place returns location_unresolved; correct the place or use known coordinates rather than dropping the location."Output schema / properties / applied_filters / properties / date_matchAdded value: +{
+ "enum": [
+ "overlap",
+ "starts_within"
+ ],
+ "type": "string"
+}Output schema / properties / applied_filters / properties / include_unknown_pricesAdded value: +{
+ "type": "boolean"
+}search_events1 field changedInput schema / properties / sort / descriptionPrevious value: -"Ordering axis. Results are always grouped chronologically by calendar day (in `timezone`); `sort` orders WITHIN each day. 'date' (default) = by start time; 'distance' = nearest first; 'demand' = most popular first; 'relevance' = semantic score first (best with query_text)."New value: +"Ordering axis. Results are presented by calendar day in timezone; sort orders within each day. With query_text and no explicit sort (or relevance), the server selects the strongest event-text and venue-vibe matches before applying that day order. Explicit date, distance, or demand sorts select by day and that axis. Without query_text, default date is chronological."search_events1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "required": [
+ "applied_filters"
+ ]
+ },
+ {
+ "required": [
+ "error"
+ ]
+ }
+ ],
+ "properties": {
+ "applied_filters": {
+ "additionalProperties": false,
+ "properties": {
+ "categories": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "center": {
+ "anyOf": [
+ {
+ "items": {
+ "type": "number"
+ },
+ "maxItems": 2,
+ "minItems": 2,
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "d_half_miles": {
+ "type": "number"
+ },
+ "date_end": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "date_start": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "density_class": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "limit": {
+ "type": "integer"
+ },
+ "local_only": {
+ "type": "boolean"
+ },
+ "max_cost": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "max_events_per_venue": {
+ "type": "integer"
+ },
+ "min_cost": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "original_radius_miles": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "original_strict_tags": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "query_text": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "radius_miles": {
+ "type": "number"
+ },
+ "relaxed": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "soft_tags": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "sort": {
+ "type": "string"
+ },
+ "sort_requested": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "strict_tags": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "error": {
+ "type": "string"
+ },
+ "results": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "age": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "category": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cost_numeric": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "cost_text": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "end": {
+ "format": "date-time",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "image_url": {
+ "format": "uri",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "is_free": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "slug": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "start": {
+ "format": "date-time",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "format": "uri",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "venue": {
+ "additionalProperties": false,
+ "properties": {
+ "city": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "distance_miles": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "state": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "vibeTags": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "name",
+ "city",
+ "state",
+ "vibeTags",
+ "distance_miles"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "title",
+ "slug",
+ "description",
+ "start",
+ "end",
+ "cost_text",
+ "is_free",
+ "cost_numeric",
+ "age",
+ "category",
+ "url",
+ "image_url",
+ "venue"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "validation_errors": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "field": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "field",
+ "message"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "results"
+ ],
+ "type": "object"
+}search_events5 fields changedInput schema / properties / categories / items / enumPrevious value: -[
- "music",
- "karaoke",
- "sports",
- "comedy",
- "theater",
- "trivia-games",
- "food-drink",
- "arts-culture",
- "community"
-]New value: +[
+ "music",
+ "karaoke",
+ "sports",
+ "comedy",
+ "theater",
+ "trivia-games",
+ "food-drink",
+ "arts-culture",
+ "community",
+ "festivals"
+]Input schema / properties / date_start / descriptionPrevious value: -"ISO-8601 start of the search window. Default: now. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight."New value: +"ISO-8601 start of the search window. Default: now. For 'tonight' pass now. For 'this weekend' pass the upcoming Saturday midnight. NOTE: the window matches by OVERLAP — an event that STARTED before date_start but is still running during the window (multi-day festival, a show that ends after midnight) is included. Filter client-side on `start` if you strictly need events that begin inside the window."Input schema / properties / sortAdded value: +{
+ "description": "Ordering axis. Results are always grouped chronologically by calendar day (in `timezone`); `sort` orders WITHIN each day. 'date' (default) = by start time; 'distance' = nearest first; 'demand' = most popular first; 'relevance' = semantic score first (best with query_text).",
+ "enum": [
+ "date",
+ "distance",
+ "demand",
+ "relevance"
+ ],
+ "type": "string"
+}Input schema / properties / state_hintAdded value: +{
+ "description": "Two-letter state abbreviation to disambiguate place_name (e.g. place_name 'Frederick' + state_hint 'MD'). Unnecessary when place_name already contains the state.",
+ "type": "string"
+}Input schema / properties / timezoneAdded value: +{
+ "description": "IANA timezone (e.g. 'America/New_York') used for the calendar-day grouping of results. Default UTC — pass the user's local zone so 'today/tomorrow' day buckets match their clock.",
+ "type": "string"
+}250,000+ real, local, future events, ranked for the signed-in person. Free to connect.
Search 190k+ US live events; every ticket bought funds animal-shelter supplies at no extra cost.
Live events in 50 cities: AI/tech meetups, hackathons, conferences, concerts. Free, read-only.
Real local places, events, and movie/TV picks, plus decision-maker games (wheel, dice, bracket).
Add one secure layer between your agents and this server.