Toolsets

A Toolset allows you to logically group multiple tools together so they can be loaded and managed as a single unit. You can define Toolsets as documents in your tools.yaml file.

This is especially useful when you are building a system with multiple AI agents or applications, where each agent only needs access to a specific subset of tools to perform its specialized tasks safely and efficiently.

Defining Toolsets

In your configuration file, define each toolset by providing a unique name and a list of tools that belong to that group..

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

Using toolsets with MCP Toolbox Client SDKs

Once your toolsets are defined in your configuration, you can retrieve them directly from your application code. If you request a toolset without specifying a name, the SDKs will default to loading every tool available on the server.

Here is how to load your toolsets across our supported languages:

Python

# Load all tools available on the server
all_tools = client.load_toolset()

# Load only the tools defined in 'my_second_toolset'
my_second_toolset = client.load_toolset("my_second_toolset")

Javascript/Typescript

// Load all tools available on the server
const allTools = await client.loadToolset()

// Load only the tools defined in 'my_second_toolset'
const mySecondToolset = await client.loadToolset("my_second_toolset")

Go

// Load all tools available on the server
allTools, err := client.LoadToolset("", ctx)

// Load only the tools defined in 'my_second_toolset'
mySecondToolset, err := client.LoadToolset("my-toolset", ctx)