Ticket set cluster
ticket_set_clusterSet which cluster an existing board ticket targets, or clear it with clear true. Identify the ticket by ticket_number or ticket_id, and the cluster by cluster_name or cluster_id (defaults to the session's cluster when the chat is opened from one). Use this the moment an investigation narrows a ticket to one cluster - a ticket filed across several clusters, or filed board-level with the cluster only named in its body, is dispatched into a session with NO cluster-scoped tools, so its agent can plan the work and then cannot execute it. Binding the ticket is what makes the next work run cluster-scoped and gives it the kubernetes, addon and stack tool families. Archived clusters are refused.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ticket_set_cluster"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| clear | No | Clear the ticket's cluster instead of setting one (default false). | |
| ticket_id | No | The ticket UUID. Optional when ticket_number is given. | |
| cluster_id | No | The target cluster's UUID. Optional when cluster_name is given. | |
| cluster_name | No | The target cluster's name. | |
| ticket_number | No | The per-organisation ticket number. |