Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions build/workforces/build-an-ai-workforce/add-tools.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,30 @@

For example, you might connect a tool that sends an email to another tool that summarizes responses, creating an automated follow-up workflow.

## Managing tools in your workforce

Once tools are added to your workforce, you can manage them directly from the agent node configuration panel.

### Accessing tool management

1. Click on an agent node to open the configuration panel
2. In the right sidebar, navigate to the **Tools** section
3. Each listed tool shows a set of available actions

### Available tool actions

- **Edit tool**: Opens the tool builder to modify the tool's code, steps, and configuration. This gives you quick access without leaving the workforce context.

Check warning on line 63 in build/workforces/build-an-ai-workforce/add-tools.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

5 settings listed as bullet points — consider using a table instead so they're easier to scan. [technical: 5 consecutive bullet items matching **Key**: value or **Key** — value pattern]
- **Disable**: Temporarily prevents the agent from using the tool without removing the connection
- **Duplicate**: Creates a copy of the tool in your project
- **Swap**: Replaces the tool with a different one while preserving the connection configuration
- **Delete**: Removes the tool and its connection from the agent

### Editing shared tools

When you click **Edit tool** for a tool used by multiple agents, a warning banner appears in the tool editor showing how many agents are affected.

If you need agent-specific modifications, clone the tool first to avoid changing behavior for other agents. See [Editing shared tools](/build/tools/create-a-tool#editing-shared-tools) for details on the cloning workflow.

## Edge Settings for Tool Connections

When connecting tools in your Workforce, you can configure the following edge settings:
Expand All @@ -69,7 +93,7 @@
The ability to connect tools directly to other tools is what makes the Workforce Builder so powerful. This workflow-style approach allows you to:

1. Create sequential processes where each tool performs a specific function
2. Build complex automations without writing code

Check warning on line 96 in build/workforces/build-an-ai-workforce/add-tools.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/workforces/build-an-ai-workforce/add-tools.mdx#L96

Did you really mean 'automations'?
3. Easily modify or replace individual components without disrupting the entire workflow
4. Maintain a visual representation of your business processes

Expand All @@ -84,7 +108,7 @@
3. Connect the condition to other tools
4. Configure the condition logic (e.g., "only send email if day of week is weekday")

Conditions act as IF statements in your workflow, allowing for branching logic and more sophisticated automations.

Check warning on line 111 in build/workforces/build-an-ai-workforce/add-tools.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/workforces/build-an-ai-workforce/add-tools.mdx#L111

Did you really mean 'automations'?

## Best Practices for Tools in Workforce Builder

Expand All @@ -95,6 +119,8 @@
3. **Document connections**: Use the description fields to explain how tools should work together
4. **Test thoroughly**: Before deploying, test your tool connections with various inputs
5. **Monitor performance**: Regularly review how your tools are performing and refine as needed
6. **Use Edit tool for quick modifications**: Click **Edit tool** from an agent's **Tools** section to open the tool builder directly within the workforce context, without navigating away
7. **Clone before editing shared tools**: If you need agent-specific changes to a tool used by multiple agents, clone the tool first — editing a shared tool affects all agents using it

## Related Features

Expand Down

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think leave this out - not really needed here, clutters it up

Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,28 @@
3. Click and drag from the agent's output connector to the input connector of your desired tool
4. Once connected, click on the connecting line (edge) to access configuration settings

## Managing tools in agent configuration

Once tools are connected to an agent, you can manage them from the agent configuration panel.

### Accessing tool management

1. Open your workforce in the Workforce interface
2. Click on the agent node to open the configuration panel
3. Navigate to the **Tools** section in the right sidebar

### Available tool actions

For each tool listed in the configuration panel, you can:

- **Edit tool**: Opens the tool builder where you can modify the tool's code, steps, and configuration without leaving the workforce context

Check warning on line 39 in build/workforces/workforce-features/agent-to-tool-configuration.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

5 settings listed as bullet points — consider using a table instead so they're easier to scan. [technical: 5 consecutive bullet items matching **Key**: value or **Key** — value pattern]
- **Disable**: Temporarily prevents the agent from using the tool without removing the connection
- **Duplicate**: Creates a copy of the tool
- **Swap**: Replaces the current tool with a different one while preserving the connection configuration
- **Delete**: Removes the tool connection from the agent

<Warning>When you click Edit tool for a tool shared by multiple agents, a warning banner appears in the tool editor showing how many agents are affected. Clone the tool first if you want changes that only apply to this specific agent. See [Editing shared tools](/build/tools/create-a-tool#editing-shared-tools) for details.</Warning>

## Configuration Options

### Connection type
Expand All @@ -32,7 +54,7 @@

This option gives your agent autonomy to determine when to use the connected tool based on context and need.

- **Communication Settings**: Provide natural language instructions explaining when and how the agent should use this tool. For example: "Use this email tool when you need to send important updates to clients or when follow-up communication is required."

Check warning on line 57 in build/workforces/workforce-features/agent-to-tool-configuration.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

6 settings listed as bullet points — consider using a table instead so they're easier to scan. [technical: 6 consecutive bullet items matching **Key**: value or **Key** — value pattern]
- **Approval mode**: Configure how the agent makes decisions about tool usage:
- **Auto run**: The agent will use the tool without requiring approval
- **Approval required**: The agent will draft the tool request but wait for human approval before execution
Expand Down Expand Up @@ -97,6 +119,10 @@
- Set appropriate "Max auto runs" limits
- Make instructions more specific about when to use the tool
- Consider changing to "Approval required" mode temporarily
4. **Tool needs modification**
- Click on the agent node and navigate to the **Tools** section in the configuration panel
- Click **Edit tool** next to the relevant tool to open the tool builder
- Update the tool's code, steps, or configuration as needed, then save your changes

## Advanced Agent to Tool Configurations

Expand Down
Loading