feat(workflow): Allow ToolNode to accept JSON string or Content inputs#6065
Open
baptmont wants to merge 2 commits into
Open
feat(workflow): Allow ToolNode to accept JSON string or Content inputs#6065baptmont wants to merge 2 commits into
baptmont wants to merge 2 commits into
Conversation
Enable ToolNode to receive JSON-formatted strings or types.Content objects in workflows. This supports flexible upstream formats, such as output from LLM agents or raw user content, automatically parsing them into dictionary arguments for downstream tools.
Collaborator
|
Response from ADK Triaging Agent Hello @baptmont, thank you for contributing this PR! This looks like a great enhancement to I noticed that the automated You can run it manually across all files using: pre-commit run --all-filesMore details about the development setup and code formatting can be found in our Contribution Guidelines. This will help us get your pull request reviewed and merged more quickly. Thank you! |
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.
Please ensure you have read the contribution guide before creating a pull request.
Link to Issue or Description of Change
1. Link to an existing issue (if applicable):
2. Or, if no issue exists, describe the change:
Problem:
Previously,
ToolNodein ADK workflows required input to be strictly a PythondictorNone. This limited workflow flexibility, preventing users from chaining aToolNodedirectly downstream of nodes (like LLM Agents or custom function nodes) that output inputs as serialized JSON strings ortypes.Contentobjects without manual parsing boilerplate.Solution:
Enhanced
ToolNode._run_implin _tool_node.py to dynamically coerce input formats before tool execution:types.Contentwhen received.json.loadsif received.Noneto{}.TypeErrorfor non-dictionary representations (e.g. lists, invalid JSON).Testing Plan
Unit Tests:
Pytest Summary:
Manual End-to-End (E2E) Tests:
Verified all workflow tests pass locally with no regressions:
Checklist