ToolDef class for dynamically creating tool definitions #719
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.
This PR introduces a
ToolDef
class for creating tools dynamically.Previously, tools could only defined using
@tool
decorators and documentation comments. It's now possible to create a tool dynamically from any function by creating aToolDef
. For example:This is effectively what happens under the hood when you use the
@tool
decorator. There is one critical requirement for functions that are bound to tools usingToolDef
: type annotations must be provided in the function signature (e.g.x: int, y: int
).ToolDef
can generally be used anywhere thatTool
can be used (use_tools()
, settingstate.tools
, etc.)