ncloud-gov-mcp-server

ncloud_nks_update_node_pool_taint

Idempotent

Replace all taints on a Node Pool in an NKS cluster to manage pod scheduling. Input cluster UUID, instance number, and key/value/effect taint objects to update.

Instructions

Update taints on a node pool in an NKS cluster (PUT replaces all taints)

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": {
      "clusterUuid": "<clusterUuid>",
      "instanceNo": "<instanceNo>",
      "taints": "<taints>"
    },
    "name": "ncloud_nks_update_node_pool_taint"
  }
}

Input Schema

Name	Required	Description
`taints`	Yes	Taint key/value/effect objects
`instanceNo`	Yes	Node pool instance number
`clusterUuid`	Yes	UUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations (idempotentHint=true, destructiveHint=false), the description discloses the PUT semantics that all existing taints are replaced, which is critical to avoid unintended loss. This adds meaningful behavioral context beyond what annotations alone provide.

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, front-loaded sentence that efficiently conveys both the action and the key replacement behavior. No filler or redundant information.

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

Completeness4/5

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

For a relatively simple three-parameter update tool, the description covers the essential purpose and the critical nuance of full replacement. Without an output schema, return values are not detailed, but the primary behavior is sufficiently explained.

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?

The input schema already provides descriptions for all three parameters, achieving 100% coverage. The description does not elaborate on parameter meanings or formats beyond the schema, so the baseline score of 3 is appropriate.

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 the verb 'Update', the resource 'taints on a node pool in an NKS cluster', and distinguishes from sibling tools like update_node_pool_label or update_node_pool by focusing specifically on taints. The parenthetical 'PUT replaces all taints' adds crucial scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys a clear context: this tool is for updating taints, and the note that it replaces all taints implies the agent must include the full desired list. While it doesn't explicitly name alternatives, the specificity to taints among siblings makes the usage context clear without exclusion criteria.

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

Deploy Server