Skip to main content
Glama

Delete node group

delete_node_group
Destructive

Delete a worker node group from an Ankra-provisioned self-managed cluster: every node in the group and its Kubernetes membership are terminated and removed permanently, one node at a time, each drained through its PodDisruptionBudgets first; a node whose drain is refused is kept, together with the group, and the operation fails naming what refused it. Workloads that can only run on this group become unschedulable. This cannot be undone - re-adding a group with the same name creates fresh, empty nodes. Call list_node_groups first and confirm the group with the user.

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": {
      "group_name": "<group_name>"
    },
    "name": "delete_node_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
group_nameYesNode group to delete (from list_node_groups).
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.

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?

Goes far beyond destructiveHint=true: it discloses sequential one-node-at-a-time deletion, PDB-gated draining, the partial-failure contract (refused drain keeps the node and group and the operation fails naming the refuser), side effects on workloads, and irreversibility including that re-adding the name yields fresh empty nodes.

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 action and scope, then layered detail on execution and failure. It is dense, semicolon-chained prose in a single sentence, which is harder to scan than bulleted clauses, but almost every clause carries real operational information.

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 destructive, non-idempotent mutation with no output schema, it covers what is destroyed, ordering, failure mode, and post-conditions. It does not mention required permissions or the response on success, which are the remaining gaps.

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, group_name and cluster_name are already documented. The description adds only the provenance hint for group_name (from list_node_groups) and the self-managed scope constraint; it adds no new syntax or format 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?

States a specific verb and resource ('Delete a worker node group') plus the precise scope: 'Ankra-provisioned self-managed cluster', which separates it from the managed-pool siblings like delete_managed_node_pool.

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 an explicit prerequisite and workflow: 'Call list_node_groups first and confirm the group with the user.' It does not name the alternative tool to use for managed node pools, so the when-not-to-use case is only implied by the 'self-managed' scoping.

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.