Skip to main content

Agent Tool

The Agent Tool Node in the XpertAI platform's Workflow serves as a callable tool for an Agent, executing a predefined sub-workflow to accomplish specific tasks when triggered.

Compared to the Task Handover nodeโ€™s single-task transfer mode, the Agent Tool Node can, upon invocation:

  • Execute multi-step, complex sub-workflows
  • Invoke multiple functional nodes
  • Branch or loop based on task results

This makes it highly suitable for scenarios requiring multi-step processing or complex logic orchestration.

How It Worksโ€‹

  1. Tool Registration and Invocation

    • The Agent Tool Node can be registered as an โ€œavailable toolโ€ by any higher-level Agent.
    • The higher-level Agent can actively call this tool node to perform specific tasks during task processing.

  2. Connecting Sub-Workflows

    • The Agent Tool Node can connect to a single subsequent node or multiple nodes to form a complete sub-workflow.

    • Sub-workflows can include:

      • Data processing nodes
      • Computation and analysis nodes
      • External API calls
      • File/database operations
      • Interactions with other agents

  3. Task Context Passing

    • When called, the Agent Tool Node receives contextual information (task content, variables, history, etc.) from the upstream Agent.
    • All nodes within the sub-workflow can access and utilize this contextual information.

  4. Task Completion and Result Return

    • After the sub-workflow is executed, the Agent Tool Node returns the processing results to the calling Agent or passes them to subsequent nodes in the main workflow (if the tool is an endpoint).

Configuration Detailsโ€‹

After adding an Agent Tool Node in the Workflow editor, the following configurations are available:

Configuration ItemDescription
Node NameCustom display name for the node in the workflow
Node DescriptionCustom description for the node in the workflow
Tool NameName of the tool for reference during Agent invocation
Tool DescriptionFunctional description for reference during Agent invocation
Input ParametersDefine variables and data that can be passed during invocation
Sub-Workflow StructureConfigure connected sub-nodes and their execution logic
EndpointSpecify if the tool is an endpoint; if so, the Agent response ends or proceeds to subsequent Agent nodes

Use Case Examplesโ€‹

1. Data Processing and Analysis Toolโ€‹

  • Main Agent receives a task to โ€œgenerate a market analysis report.โ€

  • Calls the Agent Tool Node to execute a sub-workflow:

    1. Data Collection Node โ†’ Retrieve raw data
    2. Data Cleaning Node โ†’ Remove outliers
    3. Visualization Generation Node โ†’ Output charts

2. Automated Content Generation Toolโ€‹

  • Main Agent is responsible for planning a marketing campaign.

  • Calls the Agent Tool Node to execute:

    1. Copywriting Node โ†’ Generate initial draft
    2. Language Polishing Node โ†’ Refine expression
    3. Image Generation Node โ†’ Provide accompanying visuals

3. Business Approval Sub-Workflowโ€‹

  • Main Agent receives a โ€œleave requestโ€ task.

  • Calls the Agent Tool Node to execute:

    1. Check leave balance
    2. Send approval request
    3. Notify applicant of approval result

Advantagesโ€‹

  • Highly Scalable: Supports sub-workflows of any complexity
  • Multi-Function Integration: Can call external APIs, databases, and other tools
  • Context Integrity: Ensures tasks in the sub-workflow align with the main workflowโ€™s information
  • Reusability: A single Agent Tool Node can be invoked by multiple different Agents

Best Practicesโ€‹

  1. When designing an Agent Tool Node, clearly define functional goals to avoid overly scattered logic.
  2. Use reusable functional nodes in sub-workflows to facilitate cross-scenario invocation.