Configuration

The primary way to configure Toolbox is through the tools.yaml file. If you have multiple files, you can tell toolbox which to load with the --tools-file tools.yaml flag.

Using Environment Variables

To avoid hardcoding certain secret fields like passwords, usernames, API keys etc., you could use environment variables instead with the format ${ENV_NAME}.

  user: ${USER_NAME}
  password: ${PASSWORD}

A default value can be specified like ${ENV_NAME:default}.

  port: ${DB_PORT:3306}

Sources

The sources section of your tools.yaml defines what data sources your Toolbox should have access to. Most tools will have at least one source to execute against.

kind: sources
name: my-pg-source
type: postgres
host: 127.0.0.1
port: 5432
database: toolbox_db
user: ${USER_NAME}
password: ${PASSWORD}

For more details on configuring different types of sources, see the Sources.

Tools

The tools section of your tools.yaml defines the actions your agent can take: what type of tool it is, which source(s) it affects, what parameters it uses, etc.

kind: tools
name: search-hotels-by-name
type: postgres-sql
source: my-pg-source
description: Search for hotels based on name.
parameters:
  - name: name
    type: string
    description: The name of the hotel.
statement: SELECT * FROM hotels WHERE name ILIKE '%' || $1 || '%';

For more details on configuring different types of tools, see the Tools.

Toolsets

The toolsets section of your tools.yaml allows you to define groups of tools that you want to be able to load together. This can be useful for defining different sets for different agents or different applications.

kind: toolsets
name: my_first_toolset
tools:
  - my_first_tool
  - my_second_tool
---
kind: toolsets
name: my_second_toolset
tools:
  - my_second_tool
  - my_third_tool

Prompts

The prompts section of your tools.yaml defines the templates containing structured messages and instructions for interacting with language models.

kind: prompts
name: code_review
description: "Asks the LLM to analyze code quality and suggest improvements."
messages:
  - content: "Please review the following code for quality, correctness, and potential improvements: \n\n{{.code}}"
arguments:
  - name: "code"
    description: "The code to review"

For more details on configuring different types of prompts, see the Prompts.

Explore Configuration Modules