Skip to main content
Glama

Ticket set cluster

ticket_set_cluster
Destructive

Set 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

NameRequiredDescriptionDefault
clearNoClear the ticket's cluster instead of setting one (default false).
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
cluster_idNoThe target cluster's UUID. Optional when cluster_name is given.
cluster_nameNoThe target cluster's name.
ticket_numberNoThe per-organisation ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the destructiveHint=true and idempotentHint=false annotations, it discloses useful behavior: the target cluster defaults to the session's cluster, archived clusters are refused, and an unbound ticket is dispatched into a session that has no cluster-scoped tools. It does not say what happens to a previously bound cluster when the binding is replaced, which matters given the destructive hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded with the action and the clearing option. The second sentence is long and dense, but its detail about the downstream consequence (a clusterless session) is the strongest justification for using the tool, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation with no output schema, the definition covers selection rules, defaults, refusal behavior, and motivation adequately. The remaining gaps are how the tool behaves when re-binding an already-bound ticket and what the response contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains all five parameters. The description still adds real value: it presents the parameters as either/or pairs and documents the fallback default for cluster_name/cluster_id. By the baseline, 3 is the appropriate score when the schema carries most of the meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Set which cluster an existing board ticket targets, or clear it with clear true.' It also scopes the tool to the existing board ticket, which separates it from cluster-creation or ticket-creation siblings such as file_ticket or create_support_ticket.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a strong when-to-use trigger ('the moment an investigation narrows a ticket to one cluster') and concrete motivating cases (a ticket filed across several clusters, or filed board-level with the cluster named only in the body). It also states a when-not for archived clusters. The only missing piece is that it never names a sibling alternative to use instead, in the way good alternatives guidance would.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.