Skip to main content
Glama

drain-node

Drain a Kubernetes node for maintenance by safely evicting pods, with options to force drain or ignore DaemonSets.

Instructions

Drain a node for maintenance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesThe name of the node to drain
forceNoForce drain even if there are unmanaged pods
ignore_daemonsetsNoIgnore DaemonSet pods during drain

Implementation Reference

  • Executes the drain-node tool by running the 'kubectl drain' command with optional force and ignore-daemonsets flags, returning the command output.
    case "drain-node": {
      const { node, force = false, ignore_daemonsets = true } = args;
      const forceArg = force ? "--force" : "";
      const ignoreArg = ignore_daemonsets ? "--ignore-daemonsets" : "";
      const cmd = `kubectl drain ${node} ${forceArg} ${ignoreArg} --delete-emptydir-data`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || `Node ${node} drained successfully` }]
      };
    }
  • Tool definition including name, description, and input schema for the drain-node tool, used for registration and validation.
      name: "drain-node",
      description: "Drain a node for maintenance",
      inputSchema: {
        type: "object",
        properties: {
          node: { 
            type: "string",
            description: "The name of the node to drain"
          },
          force: { 
            type: "boolean",
            description: "Force drain even if there are unmanaged pods"
          },
          ignore_daemonsets: { 
            type: "boolean",
            description: "Ignore DaemonSet pods during drain"
          }
        },
        required: ["node"]
      }
    },
  • server.js:1392-1394 (registration)
    Registers the list of all tools, including drain-node, for the ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing critical behavioral traits. It doesn't mention that draining typically involves evicting pods, potential service disruption, safety considerations, or what happens after draining (e.g., node becomes unschedulable). This is inadequate for a potentially destructive operation.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and purpose, making it immediately understandable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that performs node draining (a potentially disruptive cluster operation) with no annotations and no output schema, the description is insufficient. It doesn't explain what draining entails, typical outcomes, or safety considerations, leaving significant gaps in understanding.

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%, so parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying the 'node' parameter through context. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('drain') and resource ('a node') with the specific context 'for maintenance'. It distinguishes from sibling tools like 'cordon-node' and 'uncordon-node' by specifying the maintenance purpose, though it doesn't explicitly contrast with them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'cordon-node' or 'uncordon-node', nor are prerequisites or typical maintenance scenarios mentioned. The description only states what it does without contextual usage advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server