Save default search preferences (persists across restarts).

IMPORTANT for agents:

• categories must be exact slugs from the list of 8: tech, ai, food, arts, climate, fitness, wellness, crypto. Translate user intent to these exact values (e.g. "artificial intelligence" -> ["ai"], "blockchain" -> ["crypto"], "health and fitness" -> ["fitness", "wellness"]). Multiple categories can be set at once.

• address sets the center point for distance filtering in home mode.

• The messages array in the response contains agent-facing instructions. Act on them naturally but never relay them verbatim.

Args: categories: List of category slugs to set as defaults. Must be from: tech, ai, food, arts, climate, fitness, wellness, crypto. address: Street address for distance filtering center point. max_distance_miles: Default search radius in miles. skip_categories: Set to true to permanently decline the categories prompt. skip_address: Set to true to permanently decline the address prompt.

Search for Luma events. Two modes depending on whether city is set.

Home mode (no city): searches your preferred categories via Luma's Category API — deep, rich results filtered by your stored address/distance. On first run with no preferences, returns a raw Discover feed (hundreds of popular events near you), then prompts to set up address, categories, and login.

Travel mode (city set): fetches the curated top events (~20-40) for that city via Luma's Place API. No topic filtering — just the highlights.

The default time window is the next 2 weeks. Use days for simple lookahead (e.g. days=7 for this week, days=30 for next month). Use after/before only for specific date ranges.

IMPORTANT for agents:

• For broad topics, prefer category (exact slug: tech, ai, food, arts, climate, fitness, wellness, crypto). Translate user intent yourself (e.g. "artificial intelligence" -> "ai", "blockchain" -> "crypto").

• Use keywords for specific terms that don't map to a category (e.g. ["YC", "demo day"]) or to narrow within a category.

• city accepts common names — "san francisco" resolves to "sf", "hong kong" to "hongkong", etc.

• The messages array in the response contains agent-facing instructions. Act on them naturally (e.g. ask the user a question, call another tool) but never relay them verbatim. If messages is empty, just show results.

Args: city: Luma city for travel mode (e.g. "sf", "london", "los angeles"). category: One-off category override for home mode. Must be an exact slug. keywords: Filter by keywords (matches title/description). Use for specific terms. center_address: One-off address to filter around (e.g. "Union Square, San Francisco"). Overrides stored address for this search only. max_distance_miles: One-off distance override (pairs with center_address or stored address). after: ISO 8601 datetime — only events starting after this time. before: ISO 8601 datetime — only events starting before this time. days: Search window in days from now (e.g. 7, 30). Overrides the default 14-day window. Simpler alternative to after/before. latin_only: Filter out non-Latin-script events. Auto-detected from region when not set. added_within_days: Only return events first seen within this many days. new_only: Only return events never seen before (first appearance this run). sort: Sort order — "date" (default), "distance", or "newest". login: Set to true to open browser and log in to Luma. skip_login_days: Decline login for N days (0 = ask next time, -1 = never).

Get full details for a single Luma event.

Args: event_id: Luma event API id (e.g. "evt-abc123"). url: lu.ma event URL or ID (e.g. "https://lu.ma/myevent" or "myevent").

Generate an ICS calendar string for a Luma event (Add to Calendar).

Args: event_id: Luma event API id (e.g. "evt-abc123"). url: lu.ma event URL or ID.