ncloud-gov-mcp-server

ncloud_nks_upgrade_node_pool

Upgrade a node pool's Kubernetes version by providing cluster UUID, instance number, and target K8s version. Optionally set maxSurge and maxUnavailable to control rolling update behavior.

Instructions

Upgrade the Kubernetes version of a node pool. Uses PATCH with query parameters.

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>",
      "k8sVersion": "<k8sVersion>"
    },
    "name": "ncloud_nks_upgrade_node_pool"
  }
}

Input Schema

Name	Required	Description
`maxSurge`	No	Max nodes added during upgrade (default: 1)
`instanceNo`	Yes	Node pool instance number
`k8sVersion`	Yes	Target Kubernetes version
`clusterUuid`	Yes	UUID of the cluster
`maxUnavailable`	No	Max unavailable nodes during upgrade (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations are empty, so the description carries the full burden of behavioral disclosure. It only reveals the HTTP method (PATCH), implying mutation, but does not mention that upgrades may cause rolling node replacement, downtime, incompatibility, or irreversibility, nor whether it is a long-running operation.

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 purpose is front-loaded in a single, tight sentence with no wasted words. The second sentence about PATCH is brief but of marginal value to an MCP agent since the server typically handles the HTTP method.

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?

With no output schema and empty annotations, the description is the only source of context, and at 13 words it is insufficient for a mutating infrastructure operation. It omits expected return/status checks, version ordering constraints, upgrade disruption profile, and prerequisites such as cluster/node pool availability.

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 description coverage is 100%, so the schema fully documents all five parameters. The description adds no semantic detail about parameters beyond noting they are sent as query parameters, which is marginal; baseline 3 applies.

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 action ('Upgrade'), the resource ('node pool'), and the specific aspect (Kubernetes version). This distinguishes it from sibling tools like ncloud_nks_upgrade_cluster (which targets the whole cluster) and ncloud_nks_update_node_pool (a more general update).

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 is given on when to use this tool versus the closely related ncloud_nks_upgrade_cluster or ncloud_nks_update_node_pool, and there are no prerequisites, exclusions, or alternative recommendations. The PATCH note is an implementation detail, not usage guidance.

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

Deploy Server