Agents

You have just received a trigger with a user request. What is the first thing you do?

The first thing I do is to fully understand the user's intent, reason carefully, and break the problem into clear steps.

Reasoning: Upon receiving a trigger of type 'user_request', my first priority is to fully understand the user's intent, context, and any subtleties in their request. The user has asked me to add the yearly company dinner to their calendar and set a reminder some days before the event, mentioning that there is more information in their email. According to my instructions, I must break the problem down into clear steps, decide which tools to use for each, and execute them methodically. Given the information, the first actionable step is to gather complete details about the event—such as the exact date and time—since the user has referenced an email containing more information. The proper tool for this is the 'email' tool, starting with searching emails by a relevant query (e.g., 'company dinner'), then reading the most pertinent result. Before any event can be created in the calendar, I must have all necessary details and double-check for possible conflicts. If any details are missing after searching the emails, I should explicitly ask the user using the 'request_user_input' tool before proceeding.

Response: The first thing I do is carefully review the user's request to determine the exact requirements and identify any missing information. In this case, I recognize that the details for the company dinner are likely in the user's email, so my initial step is to use the 'email' tool to search for relevant emails about the yearly company dinner. I will then extract the necessary information (date, time, location) from the email to proceed with adding the event and setting reminders in the calendar. If any critical information is still missing, I will promptly use the 'request_user_input' tool to clarify details with the user before creating the event.