Skip to main content
Glama

Uncordon node

uncordon_node
Destructive

Uncordon one Kubernetes node: set spec.unschedulable=false so new pods can schedule onto it again. The reversal of cordon_node - use it when a cordoned node should return to service (e.g. a consolidation was abandoned, or maintenance finished). node_name must match the Kubernetes node name exactly (call get_nodes to list them); an unknown node is refused without changing anything.

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": "uncordon_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, preview the change without executing it.
node_nameYesExact name of the Kubernetes node to uncordon (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.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the mutation profile is covered. The description adds genuinely new behavioral information: an unknown node name is refused and nothing is changed, which is error-path semantics the annotations cannot express. It stops short of noting permission requirements or confirming whether the hard-coded idempotentHint=false is intentional for what is conceptually a set-to-false 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?

Three sentences, each carrying distinct load: what it does, when to use it with examples, and the failure mode. The core action and its mechanism are front-loaded, and there is no filler or restatement of the title.

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?

With only three flat parameters, full schema coverage, and annotations supplying the safety profile, the description covers the remaining gaps an agent needs: purpose, the cordon/uncordon decision, name provenance, and behavior on an invalid node. No output schema exists, so the absence of return-value detail is not a defect.

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 node_name, cluster_id, and dry_run are all documented in the schema itself, which sets the baseline at 3. The description reinforces node_name's exact-match requirement and the get_nodes discovery path, but says nothing about cluster_id or dry_run that the schema does not already say.

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 description gives a specific verb and resource (uncordon one Kubernetes node) plus the exact underlying mechanism (spec.unschedulable=false so new pods can schedule). It also distinguishes itself from the sibling cordon_node by framing itself as 'the reversal of cordon_node', so an agent can separate the two without inspecting schemas.

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?

It states the triggering condition explicitly ('use it when a cordoned node should return to service') with two concrete examples (abandoned consolidation, finished maintenance), names the inverse sibling cordon_node, and routes name discovery to get_nodes. What remains (when not to use it) is implied by the cordon/uncordon pairing.

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.