Skip to main content
Glama

Cordon node

cordon_node
Destructive

Cordon one Kubernetes node: set spec.unschedulable=true so no new pods schedule onto it. Running pods are NOT evicted - they keep running until removed (delete_pod) or drained by an operator, after which their controllers recreate them on other nodes. This is the standard first step of node consolidation: cordon the node, remove its remaining pods, and let the cluster-autoscaler or an operator reap the empty node. Note delete_pod issues a direct delete, not an Eviction-API evict, so PodDisruptionBudgets are NOT consulted - check disruption budgets and replica counts before removing pods from the node. node_name must match the Kubernetes node name exactly (call get_nodes to list them); an unknown node is refused without changing anything. Fully reversible with uncordon_node. This is the only Node mutation available to the AI assistant - patch_resource still refuses the Node kind.

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": {
      "node_name": "<node_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "cordon_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, preview the change without executing it.
node_nameYesExact name of the Kubernetes node to cordon (from get_nodes).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

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?

Beyond the destructiveHint annotation, it explains that running pods are not evicted, that delete_pod uses a direct delete bypassing the Eviction API and PodDisruptionBudgets, that unknown nodes are refused without changes, and that the operation is reversible with uncordon_node. These are consequential behavioral details not available in the annotations.

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?

The description is front-loaded with the effect and then groups non-eviction behavior, consolidation workflow, PDB caveats, node-name validation, reversibility, and sibling differentiation. It is somewhat long and includes delete_pod/PDB guidance that could arguably live with that sibling, but no sentence is filler.

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 node mutation with no output schema, the description supplies the effect, non-effects on running pods, sequencing guidance, failure behavior for unknown nodes, reversibility, and tool-selection constraints. Nothing material is missing for an agent to invoke it correctly.

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 the schema already documents dry_run, node_name, and cluster_id, including that node names come from get_nodes. The description only reinforces node_name exactness and the refusal behavior for unknown nodes, adding little parameter meaning beyond the 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?

The opening sentence names a specific verb, resource, and mechanism: cordon one Kubernetes node by setting spec.unschedulable=true. It then distinguishes the operation from uncordon_node, delete_pod, and patch_resource, so an agent can identify the tool without inspecting siblings.

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?

The description frames cordon as the standard first step of node consolidation and outlines the workflow: cordon, remove remaining pods, and let the autoscaler or operator reap the empty node. It names uncordon_node for reversal and delete_pod for pod removal, and warns to check disruption budgets and replica counts before deleting pods.

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.