update_config
Update an existing configuration by slug, creating a new version. Modify name, status, cache mode, retry settings, strategy, or targets without changing the slug.
Instructions
Update a config by slug and create a new version. Only provided fields change; name and status are editable, while the slug stays fixed. Use list_config_versions if you need history first.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Configuration slug to update | |
| name | No | New name for the configuration | |
| status | No | Configuration status | |
| cache_mode | No | Cache mode: 'simple' or 'semantic' | |
| cache_max_age | No | Cache max age in seconds | |
| retry_attempts | No | Number of retry attempts (1-5) | |
| retry_on_status_codes | No | HTTP status codes to retry on | |
| strategy_mode | No | Routing strategy | |
| targets | No | Array of target providers |
Output Schema
TableJSON 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 |