Skip to main content
Before you execute a tool, you need to discover what’s available. The catalog is how you browse toolkits and find the right tool slug — for example, finding that “send an email via Gmail” maps to GMAIL_SEND_EMAIL. Once you know the slug, you can bind it to an agent and execute it. The catalog is the set of tools available to your agents, organized into toolkits by provider. List toolkits, inspect individual tools, and discover what is available in a given scope.

Key concepts

Available toolkits

Browse the catalog

Tool lifecycle

Tools move through states so you can rely on stable behavior:

Errors

Security

Common mistakes

  • Hardcoding tool slugs without discovery. Use discover_tools to see what an agent can call in context.
  • Depending on deprecated tools. Migrate before a tool reaches retired.

Best practices

  • Discover tools by scope rather than assuming availability.
  • Pin to published tools for production workloads.
  • Watch the changelog for deprecation notices.

Connected Accounts

Authorize a provider before using its tools.

Bindings

Grant an agent access to a toolkit.

Executing Tools

Call a tool once you have found it.

Tools (concept)

The model behind the catalog.