Repository navigation
examples: add current time tool example - #798
Open
luffyIGL010 wants to merge 1 commit into
Open
luffyIGL010 wants to merge 1 commit into
luffyIGL010 wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or 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
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.
What
Adds
examples/tools-current-time.py, an example showing how to give a model aget_current_timetool, plus a unit test covering tool schema generation for afunction with a defaulted
strargument.Why
Models have no clock, so questions like "what time is it?" get guessed or wrong
answers. Tool calling is the correct fix, and there is currently no example
showing this common use case.
How I tested
llama3.1locally; the model called the tool with atimezone and answered correctly from the tool output.
tests/test_utils.py;pytestandruffpass.