-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Backport: Add Perplexity Search tool to registry and documentation #10804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Tavily code example in the registry is incomplete - it only demonstrates using
tavilySearchwithout parentheses, while the corresponding cookbook example shows using bothtavilySearch()andtavilyExtract()with parentheses.View Details
Analysis
Tavily code example in registry is incomplete and uses incorrect function syntax
What fails: The registry example for Tavily (lines ~167-179 in
content/tools-registry/registry.ts) showswebSearch: tavilySearchwithout parentheses and only demonstrates the search tool, missing the extract tool entirely. The cookbook shows both tools should be used with function invocation.How to reproduce: Look at the Tavily entry in
content/tools-registry/registry.ts:Compare to cookbook example in
content/cookbook/05-node/56-web-search-agent.mdx:Result: The registry example shows incorrect syntax that won't work -
tavilySearchwithout parentheses passes the function reference instead of calling it to return the configured tool instance. Also missingtavilyExtractfrom the example.Expected: According to official Tavily documentation, both functions must be called with parentheses:
tavilySearch()andtavilyExtract(). The registry should demonstrate both available tools like the cookbook does.Changes made: Updated the Tavily entry to:
tavilySearchandtavilyExtracttavilySearch()andtavilyExtract()