Skip to main content
Glama

Move cluster to organisation

move_cluster_to_organisation
Destructive

Move a cluster into another EXISTING organisation you belong to. Only an administrator of BOTH the current organisation and the destination can do this. The cluster, its agent, executions, resources, findings, insights, DNS and variables follow it; access grants, kube tokens, notification routes and mutes, report schedules and cluster-group memberships from the current organisation are detached; billing, audit and chat history stay behind. Only imported clusters can be moved for now: Ankra-provisioned and managed Kubernetes clusters use a provider credential that belongs to the current organisation and are refused. The move is also refused while operations are running, when the cluster is in a cluster mesh, when it has DNS zones bound to the current organisation (a published cluster domain or custom DNS zones), for playground and sandbox clusters, and when the destination already has a cluster with the same name. As a guardrail you MUST pass confirm_name exactly equal to the cluster's name - any mismatch refuses the move. Always have the user explicitly confirm the exact cluster name and the destination organisation first.

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": {
      "destination_organisation": "<destination_organisation>",
      "confirm_name": "<confirm_name>"
    },
    "name": "move_cluster_to_organisation"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
confirm_nameYesThe exact name of the cluster being moved, echoed back as the guardrail.
destination_organisationYesThe id, slug or name of the destination organisation. It must be one of the caller's own organisations, other than the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare destructive/not-idempotent/not-readonly; the description goes far beyond by enumerating exactly which dependent assets follow the cluster, which are detached (access grants, kube tokens, notification routes, mutes, report schedules, cluster-group memberships), and which stay behind (billing, audit, chat history). It also discloses the confirm_name guardrail and the full set of server-side refusal conditions, which is precisely the behavioral context an agent needs before calling a destructive mutation.

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?

Purpose is front-loaded and nearly every clause carries operative information (transfer list, detach list, refusal list, guardrail). It is a single dense block, though; splitting the refusal conditions into a list would make it easier to scan without losing any content.

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

Completeness5/5

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

For a destructive, cross-organisation migration with four parameters and no output schema, the definition covers preconditions, side effects on child resources, all known rejection cases, and the confirmation guardrail. An agent has everything needed to decide whether to call it and how to call it safely.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the destination must be one the caller belongs to and administers, and confirm_name must match exactly or the move is refused. That directly explains the purpose of the guardrail parameter rather than restating its schema text.

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?

States a specific verb and resource ('Move a cluster into another EXISTING organisation') and qualifies the scope ('you belong to'), so an agent can tell this apart from project-level or creation tools without opening the schema. The capitalised EXISTING also signals the operation is a relocation, not a provisioning step.

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?

Gives unusually explicit when-to-use and when-not-to-use guidance: admin of both organisations, only imported clusters, and a long list of refusal conditions (running operations, mesh membership, bound DNS zones, playground/sandbox, name collision). It also instructs the agent to get explicit user confirmation first. The only gap is that the adjacent sibling move_cluster_to_project is never named as the alternative for project-level moves.

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.