This repository was archived by the owner on Jul 16, 2025. It is now read-only.
feat: Google Gemini server tools #356
Merged
Conversation
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
|
Yes, another good one :) came across that with Claude as well - also called "server tools" there - so i guess the naming is good 👍 |
chr-hertel
reviewed
Jun 28, 2025
examples/google/server-tools.php
Outdated
| ); | ||
|
|
||
| // Available server-side tools as of 2025-06-28: url_context, google_search, code_execution | ||
| $response = $chain->call($messages, ['server_tools' => ['url_context' => true]]); |
There was a problem hiding this comment.
what do you think about enabling those server tools on the model class instead? feels a bit more like a feature of that model than of the chain to me
There was a problem hiding this comment.
You mean just set the $options on the model instead of the call? Sure, I'll adjust the example
valtzu
force-pushed
the
google-server-tools
branch
from
f0da350 to
cde1175
Compare
valtzu
changed the title
|
tested that all other toolcall examples still work with the new serializer setting - but with that server-tool example i always get a 429 response - guess that's due to my google setup atm |
OskarStark
added a commit
that referenced
this pull request
Jul 1, 2025
- Created detailed documentation explaining URL Context, Google Search, and Code Execution tools - Added usage examples, configuration options, and best practices - Updated README.md to reference the new documentation - Covers implementation from PR #356
OskarStark
added a commit
to symfony/ai
that referenced
this pull request
Jul 1, 2025
This PR was merged into the main branch. Discussion ---------- feat: Google Gemini server tools | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Docs? | no | Issues | | License | MIT Cherry picking php-llm/llm-chain#356 Commits ------- 88ca18a feat: Google Gemini server tools (#356)
symfony-splitter
pushed a commit
to symfony/ai-platform
that referenced
this pull request
Jul 11, 2025
This PR was merged into the main branch. Discussion ---------- feat: Google Gemini server tools | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Docs? | no | Issues | | License | MIT Cherry picking php-llm/llm-chain#356 Commits ------- 88ca18a feat: Google Gemini server tools (#356)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add support for Google server-side tools like Google search, URL context & Code execution
I thought of using
Toolclasses for this but didn't find any solution I was happy with, so went the easy way for now.Ideally no changes would've been required for this approach at all, but there were 2 issues:
new \ArrayObject()toolsincall's$options, then all toolbox tools go away – hence the newserver_tools(open to better naming –remote_tools?)If someone has already given this a thought, please share your thoughts / if there is some clear better approach