
Node Details
- Name: seqToolNode
- Type: ToolNode
- Version: 2.0
- Category: Sequential Agents
- Base Class: ToolNode
Parameters
Required Parameters
-
Tools (Tool, list)
- List of tools to be executed by the node
-
LLM Node (LLMNode)
- The Language Model node to be used for processing
-
Name (string)
- Custom name for the tool node
Optional Parameters
-
Require Approval (boolean)
- If enabled, requires approval before executing tools
-
Approval Prompt (string)
- Custom prompt for approval (only applicable if “Require Approval” is enabled)
- Default: “You are about to execute tool: . Ask if user want to proceed”
-
Approve Button Text (string)
- Text for the approve button (only applicable if “Require Approval” is enabled)
- Default: “Yes”
-
Reject Button Text (string)
- Text for the reject button (only applicable if “Require Approval” is enabled)
- Default: “No”
-
Update State (tabs)
- Options to update the state after tool execution
- Tabs: a. Update State (Table): GUI-based state update b. Update State (Code): Code-based state update
Input
- The node accepts input from a predecessor node, typically an LLM node
- Input should be in the form of AIMessages
Output
-
The node outputs ToolMessages containing:
- Tool name
- Tool input
- Tool output
- Source documents (if any)
- Artifacts (if any)
Functionality
- Tool Execution: The node executes the specified tools based on the input received.
- Approval Process: If enabled, it seeks user approval before executing tools.
- State Update: After tool execution, it can update the workflow state based on the output.
- Error Handling: Provides error messages for various scenarios like missing tools or invalid inputs.
Use Cases
- Integrating specific tools or actions within a sequential agent workflow
- Allowing user intervention before critical tool executions
- Dynamically updating workflow state based on tool outputs
Notes
- The node is part of a larger sequential agent system and is designed to work in conjunction with other nodes, especially LLM nodes.
- It supports both UI-based and code-based methods for updating the workflow state after tool execution.
- The node can handle multiple tools and execute them in parallel if needed.