Skip to main content
Glama

Move cluster to project

move_cluster_to_project
Destructive

Move a cluster into another project of the same organisation (the twin of ankra project move cluster). Needs projects.manage. The cluster's DNS zones, incidents and AI tickets follow it; a notification route of the cluster pinned to another project follows the cluster into the destination project and is reported. Refused while an operation is running on the cluster, and when the cluster is already in that project. Members who hold their access through a project assignment lose or gain the cluster with the move. Always have the user confirm the cluster and the destination project first; list_projects names the project ids.

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": {
      "project_id": "<project_id>"
    },
    "name": "move_cluster_to_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster to move. Optional when a cluster is selected.
project_idYesUUID of the destination project (from list_projects).
cluster_nameNoExact name of the cluster to move. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful side effects beyond that: DNS zones, incidents and AI tickets follow the cluster, a cross-project notification route follows and is reported, and members with project-assignment access gain or lose the cluster. That is real added context, though it does not cover reversibility or how to undo a move.

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?

Front-loaded with the operation and scope, then permissions, side effects, refusal conditions, and the confirmation step in a single dense paragraph. Every sentence carries information, though the run-on list of side effects could be split for scanability.

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, 3-parameter move with no output schema, the description covers permissions, cascading side effects, refusal conditions, access implications and the confirmation requirement. The one gap a reader might want (the returned shape) is partially signalled by 'is reported'.

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 coverage is 100%, so cluster_id, cluster_name and project_id are already documented, including the 'optional when a cluster is selected' behaviour. The description contributes only the sourcing hint for project_id (from list_projects) and the instruction to confirm both values, which is marginal against a fully-described schema.

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 scoped precisely: move a cluster into another project of the same organisation. The scope qualifier ('of the same organisation') and the CLI twin reference distinguish it from siblings like move_cluster_to_organisation and move_application_to_project without opening their schemas.

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

Usage Guidelines5/5

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

Gives explicit preconditions (needs projects.manage), explicit refusals (an operation is running on the cluster, or the cluster is already in that project), and a named helper for the missing input ('list_projects names the project ids'). It also mandates a confirmation step before calling, which is exactly the when-to-use guidance an agent needs for a destructive move.

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.