🧰 Project Toolbox
Caution
Project Toolbox is experimental and not an official Google product. This is an early access project, intended to be shared under NDA to gather feedback validate direction. You should not share or discuss this project with anyone not under NDA.
Project Toolbox is an open source server that enables developers to build production-grade, agent-based generative AI applications that connect to databases via tools.
Project Toolbox sits between your application's orchestration framework and your database, providing a control plane for both managing and invoking tools. It enables you to create database-focused tools easier, faster, and more securely.
Table of Contents
Getting Started
Installing the server
For the latest version, check the releases page and use the following instructions for your OS and CPU architecture.
Binary
# see releases page for other versions
curl https://storage.googleapis.com/genai-toolbox/v0.0.1/linux/amd64/toolbox
chmod +x toolbox
Container Images
You can also install Toolbox as a container:# see releases page for other versions
docker pull us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:$VERSION
Compile from source
To install from source, ensure you have the latest version of Go installed.
go install github.com/googleapis/genai-toolbox@v0.0.1
Running the server
Configure a tools.yaml to define your tools, and then execute toolbox to
start the server:
./toolbox --tools_file "tools.yaml"
You can use toolbox help for a full list of flags!
Using with Client SDKs
Once your server is up and running, you can load the tools into your application. See below the list of Client SDKs for using various frameworks:
LangChain / LangGraph
Once you've installed the Toolbox LangChain SDK, you can load tools:from toolbox_langchain_sdk import ToolboxClient
# update the url to point to your server
client = ToolboxClient("http://127.0.0.1/")
# these tools can be passed to your application!
tools = await client.load_toolset()
Configuration
You can configure what tools are available by updating the tools.yaml file. If
you have multiple files, you can tell toolbox which to load with the
--tools_file tools.yaml flag.
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.
sources:
my-cloud-sql-source:
kind: cloud-sql-postgres
project: my-project-name
region: us-central1
instance: my-instance-name
user: my-user
password: my-password
database: my_db
Tools
The tools section of your tools.yaml define your tools: what kind of tool it
is, which source it affects, what parameters it takes, etc.
tools:
get_flight_by_id:
kind: cloud-sql-postgres-generic
source: my-pg-instance
description: >
Use this tool to list all airports matching search criteria. Takes
at least one of country, city, name, or all and returns all matching
airports. The agent can decide to return the results directly to
the user.
statement: "SELECT * FROM flights WHERE id = $1"
parameters:
- name: id
type: int
description: 'id' represents the unique ID for each flight.
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 groups based on agent or application.
toolsets:
my_first_toolset:
- my_first_tool
- my_second_tool
my_second_toolset:
- my_second_tool
- my_third_tool
You can load toolsets by name:
# This will load all tools
all_tools = await client.load_toolset()
# This will only load the tools listed in 'my_second_toolset'
my_second_toolset = await client.load_toolset("my_second_toolset")
Versioning
This project uses semantic versioning, and uses the following lifecycle regarding support for a major version.
Contributing
Contributions are welcome. Please, see the CONTRIBUTING to get started.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.