Skip to main content
Glama

Rename stack

rename_stack
Destructive

Rename a deployed stack on the cluster. Refused while the stack has pending drafts or when the new name is already taken. The rename is pushed to the cluster's GitOps repository when one is connected. Reversible by renaming back.

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": {
      "stack_name": "<stack_name>",
      "new_name": "<new_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "rename_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYesNew name for the stack (no spaces, must not end with a hyphen).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesCurrent name of the stack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=true, idempotent=false) the description discloses the failure modes, the side effect of pushing the rename to the cluster's GitOps repository, and that the change can be undone by renaming back. That is exactly the kind of operational context annotations cannot convey.

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?

Four short sentences, front-loaded with the action and immediately followed by the refusal conditions and side effects. Nothing is padded, though the sentences could be slightly more tightly grouped around preconditions versus effects.

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 three-parameter mutation with no output schema, the description covers preconditions, remote side effects, and reversibility. It leaves unstated what the call returns and whether existing deployments or references to the old name are affected, which would be useful for a rename operation.

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 the schema already documents stack_name, new_name (including the no-spaces/no-trailing-hyphen rule) and cluster_id with a discovery hint. The only added meaning is the uniqueness constraint on new_name, which is marginal; baseline 3 applies.

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 names a specific verb and resource with scope: 'Rename a deployed stack on the cluster.' The resource ('stack') cleanly separates it from sibling renamers such as rename_project and rename_ai_endpoint without ambiguity.

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 states the operational preconditions that gate the call — refused while pending drafts exist or the new name is taken — which effectively tells the agent when it can and cannot use this tool. It does not, however, point to any alternative tool or next step (e.g., applying drafts first), so it stops short of explicit routing guidance.

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.