Skip to main content
Glama

Delete managed node pool

delete_managed_node_pool
Destructive

PERMANENTLY delete a node pool from a managed Kubernetes cluster: its nodes are drained and terminated at the cloud provider, and local data on those nodes is destroyed. The last remaining node pool cannot be deleted. Not reversible - a new pool can be added with add_managed_node_pool, but the terminated nodes are gone.

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": {
      "pool_name": "<pool_name>"
    },
    "name": "delete_managed_node_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_nameYesName of the node pool to delete (from list_managed_node_pools).
cluster_idNoUUID of the target managed cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target managed cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well beyond them: node draining, termination at the cloud provider, destruction of local data on the nodes, non-reversibility, and a hard precondition. This is exactly the operational consequence detail an agent needs before invoking 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.

Conciseness5/5

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

Three short sentences with the irreversible nature front-loaded in capitals, followed by consequences and then the precondition/remediation. Nothing is redundant and no sentence could be dropped without losing information.

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, no-output-schema mutation, the description covers impact, irreversibility, blocking conditions, and recovery. Nothing an agent needs to decide to call it, or to warn a user beforehand, is missing.

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% and all three parameters, including cluster_id/cluster_name optionality and the pool_name lookup source, are documented in the schema itself. The description adds no additional parameter-level meaning, so the 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?

"PERMANENTLY delete a node pool from a managed Kubernetes cluster" gives a specific verb, resource, and scope, and the surrounding clause about node draining/termination separates it from delete_cluster and delete_node_group. An agent can distinguish it from siblings without opening any schema.

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?

Explicitly states the blocking precondition ("the last remaining node pool cannot be deleted") and points to add_managed_node_pool as the recovery path. It does not contrast with update_managed_node_pool or say when to prefer resizing/updating over deletion, so guidance is clear but not exhaustive.

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.