Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

drain_node

Drain a Kubernetes node by cordoning it and evicting non-daemonset pods, with dry-run simulation, force deletion, and multi-cluster support.

Instructions

Cordons the node and evicts/deletes non-daemonset pods.

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": {
      "nodeName": "<nodeName>"
    },
    "name": "drain_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce deletion of pods
dryRunNoIf true, simulates the action
clusterNoTarget cluster name (default: 'default')
nodeNameYesName of the node to drain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions cordoning and pod eviction/deletion but omits important details: what happens to pods (graceful vs force), that daemonsets are untouched, node becomes unschedulable, and prerequisites or consequences of force deletion.

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 a single, efficient sentence. It is concise but could be better structured to include key behavioral context without being verbose.

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 potentially destructive mutation tool with 4 parameters and no output schema, the description lacks details on expected results, errors, prerequisites, and operation duration. It covers the high-level action but leaves significant 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 the schema already describes each parameter. The description does not add extra meaning beyond what's in the schema, meeting the baseline of 3.

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: cordon the node and evict/delete non-daemonset pods. It distinguishes from sibling cordon_node by mentioning pod eviction, but does not explicitly differentiate from other drain-related tools.

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?

The description provides no guidance on when to use this tool vs alternatives like cordon_node or taint_node. No when-to-use or when-not-to-use context is given.

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

Deploy Server

Other Tools