District

Get enriched restaurant data in bulk for multiple restaurants. This tool retrieves comprehensive enrichment information including photos, ratings, timings, and other enrichment data. This is the PREFERRED tool for getting restaurant details as it includes thumbnail_url for images. Use this tool when: - User explicitly asks for more details about specific restaurant(s) - User asks follow-up questions requiring detailed info (reviews, timings, address) - User wants to compare specific restaurants in detail - User clicks "View Details" on a search result Widget Rendering: - Widget will ONLY render when exactly 1 restaurant is requested (single res_id) - For multiple restaurants, present data in text format for comparison - For zero restaurants, no widget is shown

**[PREREQUISITE STEP]** Get dynamic filters available for dining search based on user's location. ⚠️ IMPORTANT: This tool MUST be called BEFORE using search_dining_restaurants to understand available filter options and their valid values. This API returns all available filter definitions that can be used for dining restaurant discovery, including: - Filter names and descriptions - Valid values for each filter - Importance levels - Whether filters are exhaustive and whether they have avoid counterparts ⚠️ FILTER BEHAVIOR IN search_dining_restaurants: - When you pass multiple filters to search_dining_restaurants, they are combined with AND logic - For OR logic between filter values, make separate search_dining_restaurants requests and combine the results - Example: To find "Italian OR Chinese" restaurants, call search_dining_restaurants twice (once for Italian, once for Chinese) and merge the results Without calling this tool first, you may use invalid filter values or miss important filtering options.

Fetches available event filter options for the user's city. This is the bootstrap call for event discovery — it tells you the current categories, artists, venues, event types, and localities that have upcoming events nearby. WHEN TO USE: Call this BEFORE using *search_events*, *search_event_venues* or *search_artists* whenever the user's query references a category, artist, venue, event type, or specific event name. You need the ids from this response to pass into the other tools. You may SKIP this call only when the user is asking a fully open-ended question ("what's happening this weekend") with no entity references — in that case go straight to search_events with min_date/max_date. WHAT IT RETURNS (`EventFiltersResponse` — six top-level arrays, not a generic `available_filters` list): - categories: list of {id, name} pairs for event categories. Known names include 'Comedy', 'Music', 'Theatre', 'Workshops', 'Sports', 'Activities', 'Attractions', 'Dining Experiences'. Top ~50 categories surfaced. - artists: list of {id, name} pairs for artists / comedians / musicians / bands with upcoming events in the city. Top ~50 artists by upcoming-event count. - venues: list of {id, name} pairs for venues hosting upcoming events. Top ~50 venues by upcoming-event count. - event_types: list of strings — a small fixed vocabulary, typically ['activity', 'play', 'attraction', 'dining', 'event']. Use these exact strings (lowercase) when passing event_types into search_events. - event_names: list of strings — notable event names in the city (top ~50 by popularity). - localities: list of strings — localities where events are happening. IMPORTANT: - Filter values change by location and time — ALWAYS refresh per-session, do NOT cache ids across cities or across days for time-sensitive tags. - Use the returned IDs (NOT the names) when passing category_ids / artist_ids / venue_ids to the search tools. event_types and event_names ARE passed as strings. - If the user mentions an entity that does NOT appear in this response (e.g., a niche artist not yet in the city's catalog), do NOT fabricate an id — fall back to passing event_names with the user's literal phrase, or tell the user the entity isn't found.

Fetches available movie filter options based on user's location. WHEN TO USE: Call this BEFORE using *search_movies*, *search_theatres* or *search_shows* to get the current valid filter values for the user's area. WHAT IT RETURNS: - Available filter names (e.g., genre, language, format) - Valid values for each filter (e.g., "Action", "Hindi", "IMAX") - Filter importance levels (which filters are most useful) IMPORTANT: Filter values change by location and time, so always call this first to ensure you're using current, valid options.

Get critique reviews and ratings for a specific movie from professional critics. WHEN TO USE: When you have a specific movie and want to judge more about it — e.g., to understand critical reception, read professional reviews, or see critic ratings. This helps better understand the movie's quality from a critical perspective. RETURNS: - List of critic reviews with reviewer name, review text, and source - List of critic ratings with rating value, rater name, and source - A movie may have no critique reviews — that's normal for newer or lesser-known films IMPORTANT: - Requires a valid movie_id from search_movies results

Search for artists — comedians, musicians, bands, performers — who have upcoming events in the user's city. Results are ranked by upcoming-event count (most-booked artists first). WHEN TO USE: Pick this when the user is asking WHO is performing rather than WHAT (events) or WHERE (venues). Examples: "rock artists in town", "tell me about Zakir Khan", "which Bollywood singers have upcoming shows". WORKFLOW: 1. If the user names a specific artist OR uses a genre cue → call `get_dynamic_filters_event` first to fetch valid artist_ids. 2. Map the user's phrase to filter values. 3. Call this tool. Top of list = most active artist this season. For pure browsing ("which artists are in town?") you may skip step 1 and call with only location. SUPPORTED FILTERS: Categorical (REQUIRED when the user references a corresponding entity): - artist_ids: REQUIRED when the user names a specific artist / comedian / musician / band. Resolve the name to an id from get_dynamic_filters_event. Examples: "tell me about Zakir Khan" → [<zakir-khan-id>]; "Arijit Singh upcoming shows" → [<arijit-id>]; "is Coldplay touring here" → [<coldplay-id>]. - genres: REQUIRED when the user filters by genre. Pass the genre string(s) directly — these are NOT looked up via get_dynamic_filters_event. Phrases: "rock artists" → ['rock']; "jazz musicians" → ['jazz']; "Bollywood singers" → ['Bollywood']; "EDM DJs" → ['EDM']; "Hindi comedians" → ['hindi'] (lowercase common); "classical performers" → ['classical']; "jazz and blues" → ['jazz', 'blues']. Note: the server may reject artists whose genres don't intersect — to compensate the server fetches limit×4 candidates before genre filtering. Result count: - limit: REQUIRED when the user asks for a specific count ("top 5 comedians"). Integer. Default 10. Max 25. RANKING NOTE: Artists are pre-sorted by upcoming-event count, so the first artist is the most-booked in the city. Use this to highlight a top pick. RETURNS: List of Artist objects with these fields: - Identity: artist_id, artist_name, description (short bio) - Media: image_url - Classification: artist_type (e.g., 'comedian', 'musician', 'band'), genres[] - Activity: upcoming_event_count FOLLOW-UP PATTERN: When the user asks "what shows does X have", call this tool for the artist_id, then call `search_events(artist_ids=[<that-id>])` to get the event list with dates / venues / prices. COMPOSITIONAL EXAMPLES: - "top 5 comedians in town" → genres=['comedy'] (or use category_ids on search_events for accuracy), limit=5 - "Bollywood singers performing" → genres=['Bollywood'] - "Arijit Singh's upcoming shows" → search_artists(artist_ids=[<arijit-id>]) then search_events(artist_ids=[<arijit-id>])

Search for dining restaurants using semantic search. This API is specifically designed for dining/dine-in restaurant discovery. Use this when users are looking for restaurants to visit for dining experiences. ⚠️ REQUIRED WORKFLOW: Step 1: Call get_dynamic_filters to fetch all supported filters and valid values (also explains AND/OR filter logic) Step 2: Use this tool (search_dining_restaurants) with appropriate filters from step 1 Calling this tool without first calling get_dynamic_filters may result in using invalid filter values. CRITICAL: Ask the user to visit the booking_url to unlock more offers if they would like to make a booking at this restaurant.

Search for event venues — concert halls, theatres, stadiums, comedy clubs, activity spaces, exhibition centres — that have upcoming events in the user's city. Results are ranked by upcoming-event count (busiest venues first). WHEN TO USE: Pick this over search_events / search_artists when the user is asking WHERE events happen rather than WHAT to attend or WHO is performing. Examples of "venue queries": "concert halls near me", "comedy clubs in Bandra", "where is the Coldplay concert", "is Phoenix Marketcity an events venue". WORKFLOW: 1. If the user names a venue OR a category, call `get_dynamic_filters_event` first to resolve names → ids. 2. If the user references a specific event ("where is Zakir Khan playing"), call `search_events` first to resolve the event_id, then pass it as event_ids here. 3. Call this tool with the resolved filter values. For pure proximity browsing ("any venues nearby?") you may skip step 1 and pass only max_distance. SUPPORTED FILTERS: Categorical (REQUIRED when the user references a corresponding entity): - venue_ids: REQUIRED when the user names a specific venue. Resolve from get_dynamic_filters_event. Examples: "is Phoenix Marketcity an events venue" → [<phoenix-id>]; "shows at NSCI" → [<nsci-id>]. - event_ids: REQUIRED when the user asks "where is X happening" / "venue for X event". Resolve X via search_events FIRST, then pass that event_id here. The server intersects the input event_ids with venues hosting them. Example: "where is the Coldplay concert" → search_events for 'Coldplay' → take the resulting event_id → event_ids=[<coldplay-event-id>]. - category_ids: REQUIRED when the user filters venues by category. Map the phrase to a category id from get_dynamic_filters_event. Phrases: "comedy clubs" → [<Comedy-id>]; "concert halls" / "music venues" → [<Music-id>]; "theatres" / "playhouses" → [<Theatre-id>]; "sports stadiums" / "arenas" → [<Sports-id>]; "workshop spaces" → [<Workshops-id>]; "activity spots" → [<Activities-id>]. Distance: - min_distance: REQUIRED when the user wants venues that are NOT too close. "at least X km away" / "outside the immediate neighborhood" → min_distance=X. Rare in practice. Numeric km. - max_distance: REQUIRED when the user gives a nearness cue. "nearby" / "near me" → 5; "in my area" → 10; "within X km" → X; "in the city" → omit (defaults to city-wide). Numeric km. When set, distance values in the response use real road distance (OSRM); otherwise straight-line. Result count: - limit: REQUIRED when the user asks for a specific count ("top 5", "just 3 venues"). Integer. Default 10. Max 25. RANKING NOTE: Venues are pre-sorted by upcoming-event count, so the first venue is the busiest match in the city / area. Use this to highlight the top pick. RETURNS: List of EventVenue objects with these fields: - Identity: venue_id, venue_name, web_url - Location: city, locality, latitude, longitude, distance (km) - Media: image_url - Programming: event_names[] (upcoming events at this venue), categories[] (categories of those events) COMPOSITIONAL EXAMPLES: - "comedy clubs nearby" → category_ids=[<Comedy-id>], max_distance=5 - "where is Arijit Singh playing" → search_events(artist_ids=[<arijit-id>]) → event_ids=[<resulting-event-id>] - "top 3 concert halls in the city" → category_ids=[<Music-id>], limit=3

Search for events, concerts, comedy shows, theatre plays, sports matches, workshops, attractions, and dining experiences happening in the user's city. Results are ranked by popularity (yield index, descending) and gated to upcoming events only — past events are never returned. WHEN TO USE: Discovery / browse / "what's happening" queries. Pick this over search_event_venues / search_artists when the user is asking WHAT to attend (concerts, plays, marathons) rather than WHERE (venues) or WHO (artists). WORKFLOW: 1. If the user references a category, artist, venue, event type, or specific event name → call `get_dynamic_filters_event` first to resolve those names to ids. 2. Map the user's natural-language query to filter values. 3. Call this tool. Return results ranked by popularity (top of list = most popular). For purely open-ended browsing ("anything happening this weekend?"), step 1 is optional — call directly with min_date/max_date. SUPPORTED FILTERS: Categorical (REQUIRED when the user references a corresponding entity): - category_ids: REQUIRED when user asks for a category. Map the user's phrase to the category id from get_dynamic_filters_event. Phrases: "comedy" / "stand-up" → Comedy id; "live music" / "gigs" / "concerts" → Music id; "theatre" / "plays" → Theatre id; "workshops" / "classes" → Workshops id; "sports" / "matches" / "league" → Sports id; "activities" / "things to do" → Activities id; "attractions" / "tourist spots" / "things to see" → Attractions id; "dining experiences" / "food events" / "supper clubs" → Dining Experiences id. - artist_ids: REQUIRED when user names an artist / comedian / musician / band. Resolve the name to an id from get_dynamic_filters_event. Examples: "Zakir Khan show" → [<zakir-khan-id>]; "Arijit Singh concert" → [<arijit-singh-id>]; "Coldplay tickets" → [<coldplay-id>]. - venue_ids: REQUIRED when user names a specific venue. Examples: "events at Jio World" → [<jio-world-id>]; "shows at NSCI" → [<nsci-id>]; "Phoenix Marketcity events" → [<phoenix-id>]. - event_types: REQUIRED when user uses an event-type noun. Vocabulary is the small fixed set returned by get_dynamic_filters_event — typically 'activity', 'play', 'attraction', 'dining', 'event'. Phrases: "stand-up shows", "comedy night" → ['event']; "theatre plays" → ['play']; "workshops" / "classes" / "experiences" → ['activity']; "tourist attractions" / "must-see spots" → ['attraction']; "supper clubs" / "food events" → ['dining']. - event_names: REQUIRED when user names a specific event title (and you have the id from get_dynamic_filters_event, OR you're falling back to the user's literal phrase because the entity isn't in the catalog). Examples: "book Zakir Khan Live" → ['Zakir Khan Live']; "tickets for Bangalore Marathon" → ['Bangalore Marathon']. - event_ids: REQUIRED when you already hold concrete event ids (e.g., a follow-up after search_events / search_event_venues) and want to refetch or narrow results to that exact set. Array of event id strings. - exclude_event_ids: REQUIRED when user says 'not that one' / 'anything but X' / 'exclude X' referring to specific events. Array of event id strings to exclude from results. - exclude_category_ids: REQUIRED when user says 'no comedy' / 'not music' / 'anything except sports'. Resolve each negated category to an id via get_dynamic_filters_event and pass them here. - exclude_event_types: REQUIRED when user negates an event-type noun ('not plays', 'no attractions'). Array of event-type strings drawn from the same fixed vocabulary as event_types. Pricing: - is_free: REQUIRED true when user says 'free events', 'no cost', 'free entry', 'gratis', 'no ticket needed'. Boolean. Omit when not negated. Example: "free workshops this weekend" → is_free=true. - min_price / max_price: REQUIRED when the user gives a price band or budget cue. "under ₹X" / "below ₹X" / "less than ₹X" → max_price=X. "over ₹X" / "above ₹X" / "more than ₹X" → min_price=X. "cheap" / "budget" → max_price=500. "between ₹X and ₹Y" → set both. "premium" / "high-end" → min_price=2000. Numeric INR. Date range: - min_date / max_date: REQUIRED when user references a time window. Resolve relative phrases against today's date (use Today's date below). "today" → both = today. "tomorrow" → both = today + 1. "tonight" → both = today (also consider min_price filtering or leave time-of-day to ranking). "this weekend" → min_date=upcoming Sat, max_date=upcoming Sun. "next week" → min_date=next Mon, max_date=next Sun. "this month" → min_date=today, max_date=last day of current month. "in December" → min_date=Dec 1, max_date=Dec 31 (year=current or +1 if Dec has passed). "next 7 days" → min_date=today, max_date=today + 7. Format strictly YYYY-MM-DD. Distance: - max_distance: REQUIRED when user uses a nearness cue. "nearby" / "near me" → 5 km; "in my area" → 10 km; "within X km" → X; "anywhere in the city" → omit. Numeric km. Note: there is no min_distance for events — use search_event_venues if the user wants "at least X km away". Result count: - limit: REQUIRED when user asks for a specific count ("top 5", "just 3"). Integer. Default 10. Max 25 (server caps higher values). RANKING / FRESHNESS NOTES: - Results are pre-sorted by popularity descending. The first event is the most popular match — surface it as a primary recommendation. - Only events that are PUBLIC and have not yet ended are returned. Past events are never in the response. - Distance is enriched via real road distance (OSRM) when max_distance > 0, otherwise it's straight-line. Either way the `distance` field is populated. RETURNS: List of Event objects with these fields: - Identity: event_id, name, description, brand_id, web_url - Time: date_string (human-readable), start_time_epoch, end_time_epoch - Venue: venue_name, locality, city, latitude, longitude, distance (km) - Pricing: price_string ("INR 499 onwards"), min_price (numeric), offer_string - Media: image_url, video_url - Tags & flags: tags[], sports[], is_dining_event, is_activity, is_play, is_attraction (use these to render badges or pick a render template) - Rating: rating_info {rating, review_count}, popularity_score IMPORTANT: Always present dates and times in human-readable form (e.g. "27 March 2026, 8:00 PM") when showing results to the user. Prefer date_string verbatim. COMPOSITIONAL EXAMPLES (combine multiple filter mappings in one call): - "free comedy shows this weekend" → category_ids=[<comedy-id>], is_free=true, min_date=<sat>, max_date=<sun> - "Arijit Singh concerts under ₹3000 in Bangalore" → artist_ids=[<arijit-id>], max_price=3000 - "top 5 events at Jio World next month" → venue_ids=[<jio-world-id>], min_date=<month-1st>, max_date=<month-end>, limit=5 - "theatre plays nearby tonight" → event_types=['play'], max_distance=5, min_date=<today>, max_date=<today>

Searches for movies playing in theaters near the user's location or upcoming releases. WHEN TO USE: When user wants to find movies by title, genre, cast, language, or other criteria. This tool covers both movies currently in cinema and those launching in the future. RETURNS: List of movies with details including movie_id, title, cast, duration, rating, movie detail page URL, and (when available) spotlight_thumbnail_url + spotlight_video_url — a short promo/teaser reel with still-frame preview. Prefer playing spotlight_video_url over a static poster when rendering to a widget-enabled client. IMPORTANT: Always present any dates (e.g. release_date) in human-readable form (e.g. "27 March 2026") when showing results to the user. WORKFLOW: 1. FIRST call **get_dynamic_filters_movie** to get valid categorical filter values. 2. If the user's requested movie title / actor name / director name is not found in results of get_dynamic_filters_movie (allow for some spelling mistake), assume those are upcoming movies. And decide filter values according to user input. 3. THEN call this function with appropriate filters SUPPORTED FILTERS: Categorical (get valid values from **get_dynamic_filters_movie**): - genre: e.g., "Action", "Comedy", "Drama" - language: e.g., "Hindi", "English", "Tamil" - cbfc_certification: e.g., "U", "U/A", "A" - director: Director name - actor: Actor name - movie_name: Full or partial movie title - screen_format : e.g., "2D", "3D" Numeric/Date ranges (use your judgment based on user request): - duration_minutes_lower_limit: Minimum movie length in minutes - duration_minutes_upper_limit: Maximum movie length in minutes - release_date_lower_limit: Earliest release date (format: YYYY-MM-DD) - release_date_upper_limit: Latest release date (format: YYYY-MM-DD) Exclusion (REQUIRED when user negates — not setting these is a bug): - exclude_movie_id: REQUIRED when user asks for "more movies", "other options", "different ones", "show me more". Pass the movie_id values from your previous search_movies results. - exclude_genre: REQUIRED when user says "not X", "no X", "avoid X", "nothing X" (genre). Example: "not horror" → ["Horror"]; "no action or thriller" → ["Action", "Thriller"]. - exclude_language: REQUIRED when user says "not X", "not in X" (language). Example: "not hindi" → ["Hindi"]. - exclude_actor: REQUIRED when user says "without X", "not X", "nothing with X" (actor). Example: "without Ranveer" → ["Ranveer Singh"]. Tags (values from get_dynamic_filters_movie): - movie_tags: REQUIRED for tag-driven queries. Map: "trending" / "popular right now" → ["Trending"]; "re-release" / "classic back in theatres" → ["Re Release"]; "oscar" / "awards" / "oscar-nominated" → ["Oscar Nominations"]. Count: - limit: REQUIRED when user asks for a specific count ("top 3", "just 5", "show me 10"). Integer. Default 5 if user does not specify. Status: - upcoming_only: REQUIRED for release-status queries. Set "true" for "upcoming", "coming soon", "not released yet", "future releases". Set "false" for "currently playing", "in theatres now", "running movies".