Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

uncordon_node

Mark a node as schedulable to resume pod scheduling after maintenance or repair.

Instructions

Marks a node as schedulable.

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

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, simulates the action
clusterNoTarget cluster name (default: 'default')
nodeNameYesName of the node to uncordon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavioral traits. It lacks information about idempotency (is uncordoning a non-cordoned node a no-op?), required permissions, side effects on workloads, or status codes. The description only states the effect without behavioral nuance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but lacks important usage and behavioral information. Conciseness is achieved at the expense of completeness, resulting in a minimum viable description.

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?

Given the tool has 3 parameters, no output schema, and no annotations, a single-sentence description is insufficient. It does not explain the return value, error conditions, or how 'dryRun' simulation works in practice. The description is too sparse for an agent to use reliably.

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?

All three parameters are fully documented in the input schema (100% coverage), so the description adds no extra meaning. Baseline 3 is appropriate, as the schema already conveys parameter semantics.

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 'Marks a node as schedulable' clearly states the action (marks), the resource (node), and the resulting state (schedulable). This directly contrasts with the sibling 'cordon_node', which marks a node as unschedulable.

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 usage context is provided. The description does not explain when to uncordon vs. cordon, prerequisite conditions (e.g., node must be cordoned first), or consequences. This forces the agent to infer usage from the tool name alone.

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