Skip to main content
Glama

cordon-node

Mark a Kubernetes node as unschedulable to prevent new pods from being scheduled on it, useful for maintenance or troubleshooting.

Instructions

Mark a node as unschedulable

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesThe name of the node to cordon

Implementation Reference

  • The execution handler for the cordon-node tool, which destructures the node name from input arguments, constructs and executes the 'kubectl cordon <node>' command using execAsync, and returns the command stdout or a success message.
    case "cordon-node": {
      const { node } = args;
      const cmd = `kubectl cordon ${node}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || `Node ${node} cordoned` }]
      };
    }
  • Input schema for the cordon-node tool, specifying an object with a required 'node' property of type string, describing the Kubernetes node name to cordon.
    inputSchema: {
      type: "object",
      properties: {
        node: { 
          type: "string",
          description: "The name of the node to cordon"
        }
      },
      required: ["node"]
    }
  • server.js:1127-1138 (registration)
    Registration of the 'cordon-node' tool within the tools array provided to the ListToolsRequestSchema handler. Includes tool name, description, and input schema.
    name: "cordon-node",
    description: "Mark a node as unschedulable",
    inputSchema: {
      type: "object",
      properties: {
        node: { 
          type: "string",
          description: "The name of the node to cordon"
        }
      },
      required: ["node"]
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the behavioral outcome ('Mark a node as unschedulable') but doesn't disclose important traits: whether this requires admin permissions, if it's reversible (implied but not stated), what happens to existing pods (they remain running), or any side effects. For a mutation tool with zero annotation coverage, this is insufficient.

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 that communicates the core functionality without unnecessary words. It's appropriately sized for a simple operation with one parameter.

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

Completeness3/5

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

For a single-parameter mutation tool with no annotations and no output schema, the description is minimally adequate but incomplete. It explains what the tool does but lacks behavioral context, usage guidance, and output information. Given the simplicity of the operation, it's functional but could be more helpful.

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%, with the single parameter 'node' clearly documented in the schema as 'The name of the node to cordon'. The description adds no additional parameter information beyond what the schema provides, meeting 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 ('Mark as unschedulable') and resource ('a node'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'drain-node' or 'uncordon-node', but the verb 'cordon' is specific enough in Kubernetes context to imply isolation without eviction.

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 'drain-node' (which also makes nodes unschedulable but evicts pods) or 'uncordon-node' (the reverse operation). The description lacks context about typical use cases, prerequisites, or exclusions.

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