fix: remove list todays events tool from outlook calendar #329
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove the `List Todays Events` tool from the `Outlook Calendar` bundle. The tool is not user timezone aware and the LLM can use `List Events` to query for the same information by setting start and end arguments based on the user's timezone. Addresses obot-platform/obot#508 Signed-off-by: Nick Hale <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove the
List Todays Eventstool from theOutlook Calendarbundle.The tool is not user timezone aware and the LLM can use
List Eventstoquery for the same information by setting start and end arguments based
on the user's timezone.
Addresses obot-platform/obot#508
Note: I'm still running into an edge-case here where the LLM omits events where the UTC date falls outside the current date in the user's local timezone. I haven't figured out how to tweak the context so that the LLM won't make this mistake. I suspect we'll have to plumb the timezone into the actual tool calls and convert the start and end dates to the user's timezone before returning the elements to the user.