Agents

Your first step is to break down the problem and formulate a step by step plan. What is the plan?

(1) Ask the user how many days before they want the reminder. (2) Use the email tool to search for emails about the yearly gathering. (3) Read the relevant email to extract the event date. (4) Use the calendar tool to add the event. (5) Check for any calendar conflicts. (6) Add the reminder X days before the event

Reasoning: I will treat this as a multi-step workflow: clarify any missing user preferences, retrieve authoritative details from email, validate and resolve ambiguities, check for calendar conflicts, confirm reminder lead time, create the event, and verify completion. I’ll use the email tool to find specifics (date/time/location) and the calendar tool to check conflicts and create the event. If any information is missing or unclear, I’ll explicitly ask the user via the request_user_input tool. I will keep a scratch pad noting findings and decisions at each step.

Response: Plan to add the yearly company dinner to the calendar with a reminder:

1) Initialize and capture requirements
- Create a scratch pad to track: email candidates, extracted event details (title/date/time/location), conflicts, and user preferences (reminder lead time, calendar/time zone).
- Identify missing inputs likely needed: reminder_days_before (exact number), preferred calendar (if multiple), and confirm time zone if not evident from email.

2) Retrieve event details from email
- Use email.search_emails with queries like: "company dinner", "yearly company dinner", "annual company dinner", "company dinner 2025", and sort by most recent.
- For top candidates, use email.read_email to open them and extract: event name, date (YYYY-MM-DD), start/end time, time zone, location/venue, dress code/notes, RSVP deadline, and any special instructions.
- If multiple conflicting emails exist, prefer the latest authoritative sender (e.g., HR/Events) and verify consistency.

3) Validate and resolve ambiguities
- If any key fields are missing or ambiguous (date, time, time zone, or location), or if the email is not found, use request_user_input to ask the user for the missing details or to forward the email.

4) Check calendar for conflicts
- Using the extracted event date (and time if available), call calendar.read_calendar for a range that covers the event day (e.g., start_date = event_date, end_date = event_date) or +/-1 day if exact time is unclear.
- Note any overlapping events in the scratch pad.

5) Confirm reminder preference
- If the user hasn’t specified the reminder lead time, use request_user_input to ask: “How many days before would you like the reminder?” (offer common options like 1, 2, 3, 5, or 7 days).

6) Create the calendar event
- Construct event_name (e.g., "Yearly Company Dinner" or the official title from the email).
- Call calendar.create_event with: event_name, date (YYYY-MM-DD), and reminder_days_before as confirmed by the user.
- If the email specifies a time and the tool supports only date, note the limitation and proceed with date + reminder_days_before; otherwise, include time if supported (or add to notes for user awareness).

7) Verify creation
- Re-check the calendar (calendar.read_calendar for the event date) to confirm the event appears correctly with the set reminder.

8) Report back and next steps
- Provide a concise confirmation summary to the user: event details, reminder lead time set, and any conflicts found or avoided.
- Ask if they’d like any adjustments (different reminder lead time, title tweaks, or additional notes).