Edit System Preference
cascade_edit_preferenceUpdate a single Cascade system preference by name and value; changes apply server-wide immediately. Requires system-admin credentials.
Instructions
Update a single Cascade system preference.
Accepts a preference object with name and value. The name must exactly match an existing preference key (see cascade_read_preferences for the full list); value is always sent as a string, even for numeric or boolean preferences (Cascade parses it). Changes take effect server-wide immediately. Requires system-admin-level credentials.
Args:
preference (object, required, shape varies — see Cascade docs): The preference to update
name (string, required): Exact preference key
value (string, required): New value (serialized as string even for numbers/booleans)
Returns: Cascade OperationResult: { success: true } On failure: { success: false, message: "" }
Examples:
Use when: "Increase the server's API timeout" -> { preference: { name: "api.request.timeoutSeconds", value: "60" } }
Use when: "Toggle a feature flag" -> { preference: { name: "feature.somefeature.enabled", value: "true" } }
Don't use when: You want to read current values — use cascade_read_preferences first.
Don't use when: The target is user-scoped — system preferences are server-wide.
Error Handling:
"Preference not found" when name is not a recognized key
"Invalid value" when value can't be parsed for the preference's type
"Permission denied" when credentials lack system-admin rights. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| preference | No | REQUIRED: The preference to create or update. Shape: `{ name: string, value: string }`. |