Skip to main content
Version: 2.0

Tool Configuration Management APIs

The Tool Configuration Management APIs handle reusable configurations for tools used by agents. These configurations store argument overrides and settings that can be referenced across multiple agents, with full version control support.

  • Create tool configurations with custom argument overrides
  • List configurations for each tool type
  • Update configurations with automatic versioning
  • Delete configurations or specific versions
  • Reference configurations in agent definitions

Tool configuration properties​

  • Configuration ID: Unique identifier (e.g., tcf_customer_support)
  • Name and description: Human-readable identification
  • Argument overrides: Default values or constraints for tool parameters
  • Version control: Automatic versioning on updates
  • Metadata: Custom properties for organization

Creating tool configurations​

Web Search Configuration​

CREATE A WEB SEARCH CONFIGURATION
1

Corpora Search Configuration​

CREATE A CORPORA SEARCH CONFIGURATION
1

Versioning​

Tool configurations support automatic versioning:

  1. Initial creation: Version 1
  2. Updates: Increment version automatically
  3. Version retrieval: Specify version in GET requests
  4. Version deletion: Remove specific versions
GET SPECIFIC VERSION
1

Using configurations in agents​

Reference tool configurations when creating agents:

REFERENCE CONFIGURATION IN AGENT
1

Available endpoints​

EndpointMethodPurpose
Create Tool ConfigurationPOSTCreate a reusable tool configuration
List Tool ConfigurationsGETList all configurations for a tool
Get Tool ConfigurationGETRetrieve specific configuration (with version)
Update Tool ConfigurationPATCHUpdate configuration (creates new version)
Delete Tool ConfigurationDELETERemove entire configuration
Delete Tool Configuration VersionDELETERemove specific version

Best practices​

  1. Use configurations for consistency across multiple agents
  2. Version management: Test new versions before updating agent references
  3. Descriptive naming: Use clear names indicating purpose
  4. Metadata organization: Use metadata for filtering and management
  5. Avoid deletion of versions referenced by active agents