This node reads workflows from the provided Paths and converts them into Tools. While any workflow can be used as a Tool out of the box, there are a few conventions that aim to maximize the Tool's usefulness:
- Workflow description: this is used to communicate the purpose of the tool to the agent. The more descriptive, the better.
- Output message: using the Tool Message Output node, it is possible to define the content of the Tool message that the agent receives after Tool execution. If none was specified, the agent will simply be notified that the Tool was successfully executed.
Additionally, Tools can be parameterized using Configuration nodes. As with the workflow description, it is crucial to ensure that every parameter has a meaningful name and description.
Tool workflows can also accept an arbitrary number of input tables and produce an arbitrary number of output tables, which can be defined using the Workflow Input and Workflow Output nodes respectively.
In general, a well-documented Tool workflow increases the chances that the agent will call the Tool correctly.
Tool cells provide helpful icons that indicate various characteristics of the corresponding Tool:
- Whether the Tool workflow has a description.
- Number of parameters.
- Number of input tables.
- Number of output tables.
If a workflow can't be read, a missing value will be output instead.