Update cluster
update_clusterUpdate a cluster's settings. The only updatable field today is the environment label. A cluster a create_*_cluster tool provisions carries the 'development' default, because those tools never name a label, and a default does not say what the cluster is for. A label this tool sets is recorded as a person's choice only when a member confirms this call's card in Ankra chat. Set any other way, over MCP, under autonomy or from an approved plan, it is recorded as automation and needs a person to confirm it, in the Ankra portal or on this tool's card, before off-hours stops and the cost autopilot treat it as chosen; such a call also cannot move a cluster off production, so it cannot lower the AI production floor. The label drives listing filters, environment colors and operator expectations. It does NOT move the stored criticality the insight grader keys on - change criticality deliberately if the grading denominator should move too.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"environment": "<environment>"
},
"name": "update_cluster"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cluster_id | No | Cluster UUID. Optional when the chat is already scoped to a cluster. | |
| environment | Yes | The environment label to set. |