OpenTable

Reservation date (YYYY-MM-DD). Interpret relative dates (e.g. "tomorrow") in the user's timezone. If the user did not specify a date, it should be today's date. Always use today or a future date; never use a past date.

Party size to search for restaurants. This number should be extracted from user prompt/input. If it cannot be determined from user input, ask the user for clarification instead of guessing. Minimum is 2, maximum is 20.

Reservation time in local time (24h HH:mm, e.g. "18:30"). Convert inputs like "7pm" to "19:00". If the user did not specify a time, choose a sensible default such as the next 30-minute slot (rounded up) or a meal-appropriate default (lunch = 12:00, dinner = 19:00 and etc.). If date is today, time must be >= current local time (rounded up). If date is in the future, any HH:mm is allowed.

Optional free-text search query. The term must contain: - EITHER: (A) EXACTLY ONE primary category: • cuisine (e.g., "italian") • restaurant name • dish (e.g., "sushi") • feature (e.g., "family friendly") - OPTIONALLY ONE location modifier (city, neighborhood, or area) - OR: (B) ONLY a location (city, neighborhood, or area) Rules: - Do NOT combine multiple primary categories. - Do NOT include ranking words (e.g., "best", "top", "greatest"). - Do NOT include generic words like "restaurant", "place", "spot". - Keep the phrase concise (1–3 words max). Priority when multiple primary categories are mentioned: 1. Restaurant name 2. Cuisine 3. Feature 4. Dish If both a primary category and location are used: Format: "<primary category> <location>" If only location is used: Format: "<location>"