Agents can use Tools during their execution.
Globant Enterprise AI Lab provides Public Tools that are preconfigured and available by default in every project. In addition to the Public Tools, you can define Private Tools in your project.
Each Tool is a one-to-one bridge between AI Lab and a single API operation. Therefore, when you define a Private Tool, you select exactly one HTTP verb and path from your API specification, and AI Lab exposes that operation as a Tool that the Agent can call. If you need additional operations from the same API, create a separate Tool for each one.
This is a step-by-step guide to create and test a Private Tool.
First, log in to the Globant Enterprise AI Backoffice. In the Project Dynamic combo box, select the project you want to work with; in this case, Documentation (Demo) is used.
Next, on the left side of the screen, you will find the Globant Enterprise AI Backoffice menu. In this menu, click on The Lab.
By clicking on The Lab in the Globant Enterprise AI Backoffice, a new window opens in the browser with the Globant Enterprise AI Lab.
Once inside Globant Enterprise AI Lab, you will see the Side Navigation Menu on the left edge of the screen. If the menu is collapsed, click on the arrow icon to expand it.
In this menu, select the Tools option to access the Tools Dashboard.
If no tools have been created yet, a message saying "No Tools Created" will appear. Below that message, click on the New Tool button to start the creation process.
Clicking on New Tool opens a new tab in the interface. This tab is organized into two sections:
3.1. Configuration
3.2. JSON
This tab is divided into three collapsible panels:
3.1.1. Scope
3.1.2. Information
3.1.3. Parameters
This section defines the tool’s connection to an external service. Globant Enterprise AI Lab supports dynamic data retrieval via an OpenAPI specification, enabling tools to interact with external APIs.
You must choose between two input options:
In this case, the Weather API is used. Since this API has an OpenAPI specification in JSON format, select the JSON option and paste the content in the Open API Json field.
This section controls how the tool is visually represented and identified.
It includes the following fields:
- Tool Name (required): Provide a clear and specific name that follows the structure of the OpenAPI specification. This helps the system correctly identify and use the tool’s operations. Important: You must read Configuration Tab of a Tool to understand and consider the requirements you have to meet when defining the name.
- Description (optional): Add a brief explanation of the tool’s purpose to help end users understand the tool’s purpose at a glance.
This information will appear on the tool’s card once it's created.
The Parameters section defines the inputs your tool requires to operate. These values determine how the tool processes incoming data and triggers external API requests.
In this case it is not necessary to define parameters so it is left unchanged.
After completing the Configuration section (3.1.), click on the JSON tab (3.2.) located at the right top of the interface.
This tab displays the complete configuration of the tool in JSON format.
The content in this section is automatically generated based on the information you provided in the previous steps (Scope, Information, and Parameters).
Reviewing this JSON is useful to ensure all values were correctly registered and to get a full overview of your tool's structure.
Once you’ve reviewed and confirmed the configuration, click on the Publish button located at the bottom right of the screen. This action publishes the tool, making it available for use.
However, publishing is not required to start using the tool during the Agent creation process. Every change or configuration is automatically saved in a draft. This allows the Tool to be added from the Agents & Tools to use section in the AI & Tools tab of any Agent—even if the tool has not been published yet.
Keep in mind that if you intend to publish the Agent later, all associated Tools must be published beforehand. While draft Tools can be used freely during testing and development, they must be published in order to be included in a published Agent.
Since April 2025 release.