Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

remove_taint

Remove a specific taint from a Kubernetes node by providing the node name and taint key, with optional dry run support.

Instructions

Removes a specific taint from a node by key.

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>",
      "key": "<key>"
    },
    "name": "remove_taint"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states the action without explaining side effects (e.g., scheduling impact), error conditions, or the role of the dryRun parameter.

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?

A single, well-structured sentence that directly conveys the action without unnecessary words. It is appropriately concise.

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 mutation tool with no annotations or output schema, the description is too brief. It lacks explanation of side effects, error handling, and the impact of the dryRun and cluster parameters.

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% with clear parameter descriptions. The description adds minimal value beyond identifying the 'key' parameter's role. Baseline is appropriate as schema does the heavy lifting.

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 clearly states it removes a specific taint from a node by key, using a strong verb and specifying the resource. It differentiates from sibling tools like 'taint_node' (adds taints) and other node operations.

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 on when to use this tool versus alternatives, such as 'taint_node' or 'drain_node'. Does not mention prerequisites or conditions for removal.

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