Create tools with the Agent Tool Builder application. Learn more in Agent Tool Builder application.

Tools are the most granular part of the framework that allows agents to perform tasks for users when they interact with Ed. Agents can run multiple tools based on a single user request. Learn more in Agents and Agent thought reasoning.

There are multiple types of tools, including:

  • Data retrieval tools
  • Logic block tools
  • Share values between agent tools
  • Agent Tool Builder application
  • Agent Toolset Builder application

For example, you might have a financials agent that's equipped with the following tool related to customer invoices:

  • Create invoices—A logic block tool type, that creates customer invoices based on the input values for Customer, Amount, Memo, and more derived from the user's prompt. The financials agent would execute this tool if a user told Ed, "Create James Kirk a $250.00 invoice for starship parts."
  • Retrieve unpaid invoices—A data retrieval tool type, that displays all of the open customer invoices and their amounts for the user. The financials agent would execute this tool if a user told Ed, "Show me all unpaid customer invoices."

Data retrieval tools

Data retrieval tools allow agents to find and display records for a user.

To create a data retrieval tool, specify the fields used as filter criteria needed to fetch the correct records for the user, and describe how the agent should determine the values for these fields. When an agent executes the tool, it determines the filter criteria and uses it to retrieve and display the data.

Use the Fetch Field Options subtable to specify the filter fields. The way the agent determines each field value depends on the Value Mapping Type you select for each field:

  • Prompted—These values are determined by the agent using the user's request. For example, you could have a Prompted fetch field option for the Status field. If a user requested to see a list of their inactive customers, the agent would determine that it should filter the Status field by Inactive.
  • Logic Block Output Mapping—Optionally, you can specify a Pre-Run Logic Block that runs before the any records are queried. This means that the agent can use these logic block outputs as filter values to retrieve records.
  • Tool Output Mapping—Use the output of a logic block tool executed earlier in the agent flow as a filter criteria. Learn more in Share values between agent tools. 

Data retrieval tools rely on a related application when the fetched records are displayed in the conversation window. Select the application, and the fields you want to display, on the Display Configuration page of the Agent Tool Builder application. The field labels that appear for these data items when the specified app is launched are what appear in the conversation window. In addition, Ed displays a link to this application alongside the data. When a user selects this link, the application opens with the same filters applied by default.

For example, the Directory agent is equipped with a tool to find active directory holds on their customers. This tool retrieves records from the DirectoryHolds table with the Fetch Field Options of Contact and Effective From. 

A user could tell Ed to show them all of the holds on their customer, Lumon Industries, placed after February 10. When the Directory agent executes this tool, any holds with a Contact of Lumon Industries and Effective From date of February 10 are displayed in a table in the chat interface, along with a link to view or modify those holds in the Customer Hold Manager application.

Logic block tools

Logic block tools allow agents to execute processes in the platform using a logic block. 

To create a logic block tool, define and describe the specific Input Fields required to run the logic block. When an agent executes the tool, it uses these descriptions to extract the appropriate values from the user's prompt, and use them to run the logic block.

For example, a financials agent could have a tool to create an invoice for a customer. This tool runs a logic block with input fields that include Customer, Amount, and Memo. 

A user could tell Ed to create an invoice for James Kirk in the amount of $250.00 for starship parts. Ed would then pass this prompt to the Financials agent, who would execute its invoice creation tool. The agent uses the descriptions of these input fields and the user's request to determine the following input values:

  • James Kirk, for the Customer field.
  • $250.00, for the Amount field.
  • Starship parts, for the Memo field.

The logic block then runs with these inputs, creating the invoice in the platform.

Logic block outputs

The agent uses the Output Fields of the logic block. They use these values to either determine their next steps in the agent flow, or to respond to the user.

You should configure an output that describes the details of the action that was completed, or any errors that occurred.

You can select the Shared checkbox for an output to allow the agent to use the output value in a different tool later in the agent flow. This is particularly useful when the agent needs to execute multiple tools using a specific record. Learn more in Share values between agent tools.

Share values between agent tools

Use the output of a logic block tool as a fetch field option or logic block input for a different tool later in the agent flow.

For example, each time an agent executes a tool that references a semantic search definition, the user must confirm the correct record in the chat interface before the agent flow can continue. An agent may need to perform multiple tools on a specific record based on the user prompt, such as creating invoices for a particular customer, and then displaying those invoices to the user. Rather than requiring the user to verify the correct customer record twice, you could define a Shared output on the first tool.

To define a shared output for a logic block tool, select the Shared checkbox in the Output Fields subtable.

You can then reference this output in a subsequent tool:

  • Logic block tools—In the Output Fields subtable, specify an Input Type of Mapped, and enter the exact name of the output field in the Shared Value Mapping field.
  • Data retrieval tools—In the Fetch Field Options subtable, specify a Value Mapping Type of Tool Output Mapping and enter the exact name of the output field in the Mapping field.

Agent Tool Builder application

Use the Agent Tool Builder application to create tools that can be executed by agents. 

To create a tool, it's important to write accurate descriptions of the tool itself. Agents determine which of their tools to execute based on the Agent Description Prompt. Describe the purpose and capabilities of the tool in natural language that can be understood by the agent.

General Configuration page

Use this page to define the logic block information for a logic block tool, or the table and filter criteria for a data retrieval type tool.

For logic block tools, use this page to select the logic block that runs when the tool is executed, and define the logic block's inputs and outputs.

In order for the agent to accurately generate input field values and execute the skill, you must describe their purpose and how to derive them in the Description Prompt field in the Input Fields subtable.

For logic block tools, use the Load Tool Signatures field action to automatically load the Input Fields and Output Fields of the selected logic block. By default, input field values are not required for the tool to be executed. If the tool should error if the input is required, specify an Tool Input Enforcement of Required.

For data retrieval tools, define the table to query records from. Specify the Fetch Field Options that instructs the agent how to determine the filter criteria to execute the tool.

Display Configuration page

This page is only available for data retrieval type tools.

Use this page to configure the fields and application that are displayed for the user after the data retrieval tool is executed. The Display Fields determine the columns in the table that displays in the chat interface. The Destination Application and Destination Application Setting determine the labels that display for those columns.

When a data retrieval tool is executed, a link to the application you select, including mapped filters matching the returned data, displays with the table in the conversation window.

Advanced Configuration page

This page is only available for data retrieval type tools.

Use this page to specify a Pre-Run Logic Block, and any input or output fields for that logic block. This functions similarly to a logic block tool, but always runs before the data is retrieved and displayed.

Agent Toolset Builder application

Use the Agent Toolset Builder application to create groups of agent tools. Toolsets are added to agents that can execute the tools defined in the toolset.

In order for an agent to access a tool, it must be included in a toolset. The same tool can be added to multiple toolsets. 

Create tools with the Agent Tool Builder application. After you add tools to a toolset, you can provide the toolset to an agent in the Agent Builder application.

Unlike the Agent Builder and Agent Tool Builder applications, descriptions in the Agent Toolset Builder application are not consumed by a large language model (LLM) and are for application developer use only.

Directed agents

When an agent with a Thought Reasoning of Directed is given a toolset, the order of the tools matter. On the toolset definition, list each tool in the Tools subtable in the order the agent should execute each tool.

If the agent has multiple toolsets, those must also be in order. Learn more in Agent Builder application.

MCP tools

To connect Ed to an MCP server, you must have an Agent Toolset record of type MCP Tools. 

The MCP Server Type dictates whether you are connecting to an external MCP server, or to an internal application, MCP bundle, or project. 

You do not need to configure Agent Tools for your Agent since they are provided by the MCP server. Learn more in Connect Ed to Nextworld's MCP server and Connect Ed to external MCP servers.