Tools Repository

The Tools Repository is the organization-wide catalog where all Tools are stored, managed, and made available for use across Agents.

The Tools Repository is like a shared library of skills that any Agent in your organization can use. Instead of rebuilding the same connection to your CRM system for every Agent you create, you define it once in the repository and reuse it everywhere.

This means your team can build new Agents faster, and any improvements to a shared Tool — for example, adding a new filter option to an order lookup — automatically apply to every Agent that uses it.

All Tools are stored as JSON definitions in the Tools Repository. The repository is account-scoped: all Agents within the same Dataworkz account share access to the same Tool catalog. Tools can be filtered, versioned, and reused across multiple Agents and Scenarios.

What You Can Do in the Repository

Action	Description
Browse	View all Tools, filterable by type (RAG, REST API, Relational DB, MongoDB, Snowflake, LLM, Composite, Call Agent, Dataset).
Create	Define a new Tool by selecting its type and completing its configuration form.
Edit	Update an existing Tool's description, parameters, or Implementation settings. Changes apply to all Agents using the Tool.
Test	Run a Tool directly from the repository with sample inputs to validate it before attaching it to an Agent.
Reuse	Attach any Tool to one or more Agents or Scenarios without duplicating configuration.

Tool Storage Format

Tools are persisted as JSON definitions. This makes them portable, diff-able, and easy to version-control alongside your Agent configurations.

{
  "name": "GetCustomerProfile",
  "type": "REST_API",
  "description": "Retrieves the full profile for a customer by ID.",
  "inputParameters": [
    {
      "name": "customerId",
      "type": "string",
      "description": "Unique customer ID",
      "required": true
    }
  ],
  "output": {
    "name": "customerProfile",
    "type": "CustomerProfile",
    "description": "The customer's profile data including name, email, and account status."
  }
}

Design Guidance

Keep Tools generic. Rather than creating separate GetOrderById and GetOrderByDate Tools, design a single GetOrders Tool with optional filter parameters (orderId, dateFrom, dateTo, status). This reduces repository sprawl and makes the Tool more useful across Scenarios.

Real-World Example

A financial services company builds three Agents: a Customer Advisor Agent, a Compliance Checker Agent, and an Internal Helpdesk Agent.

All three need to look up customer account details. Rather than configuring a separate database connection for each Agent, the team creates one GetAccountDetails Tool in the repository. All three Agents reference it. When the security team updates the API authentication method, they update it once in the repository — and all three Agents immediately use the updated version.

The Compliance Checker Agent also needs document retrieval. The team creates a SearchComplianceDocuments RAG Application Tool and attaches it only to the Compliance Agent's Scenarios. The other Agents are unaffected.

Related Concepts

• Tools — The interface and definition of an individual Tool

• Implementation — The backend connection configured for each Tool

• Agent Builder — The UI that surfaces the Tools Repository during Agent creation

• Scenarios — How Tools from the repository are assigned to specific Scenarios