update_config
Update a configuration by slug, applying changes to routing, cache, retry, and status settings. Each call creates a new version, preserving previous states.
Instructions
Update a config by slug; every call creates a new config version rather than overwriting, so earlier versions stay recoverable via list_config_versions. Only provided fields change: name, status, and all routing/cache/retry settings (cache_mode, cache_max_age, retry_attempts, retry_on_status_codes, strategy_mode, targets) are editable, while the slug stays fixed. Changes apply immediately to every API key and prompt referencing the config; get the slug from list_configs and review current settings with get_config before editing. Returns the config id, slug, and updated config payload.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | New name for the configuration | |
| slug | Yes | Configuration slug to update | |
| status | No | Configuration status | |
| targets | No | Array of target providers | |
| cache_mode | No | Cache mode: 'simple' or 'semantic' | |
| cache_max_age | No | Cache max age in seconds | |
| strategy_mode | No | Routing strategy | |
| retry_attempts | No | Number of retry attempts (1-5) | |
| retry_on_status_codes | No | HTTP status codes to retry on |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | Whether the tool call succeeded and returned structured data | |
| data | No | Structured success payload when ok is true | |
| error | No | Structured error payload when ok is false |