Add tool wrapper support for workflow deployments #3407
+463
−9
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.
Extends the
@tool(inputs={...}, examples=[...])decorator pattern (from PR #3398) to supportDeploymentDefinitionobjects inToolCallingNode. This allows workflow deployments to specify which parameters come from parent workflow inputs vs the LLM, matching the existing behavior for inline workflows and function tools.Review & Testing Checklist for Human
definitionfield structure is what the Vellum platform expectsdisplay_context.clientis None: The code skips adding the definition in this case (line 499 in expressions.py) - verify this doesn't cause downstream issuesweather-workflow-deployment→weatherworkflowdeployment) - confirm this is the expected behaviorNotes