ncloud-gov-mcp-server

ncloud_cdss_rolling_restart

Idempotent

Restart nodes in a CDSS cluster sequentially to prevent downtime. Enter the cluster instance number to start the rolling restart.

Instructions

Perform a rolling restart of all nodes in a CDSS cluster

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>"
    },
    "name": "ncloud_cdss_rolling_restart"
  }
}

Input Schema

Name	Required	Description	Default
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, providing a safety baseline. The description adds the behavioral scope of 'rolling restart of all nodes' but does not disclose potential service disruption, async execution, or whether the operation requires a maintenance window. No contradiction with annotations.

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, focused sentence that immediately conveys the operation and scope. It is front-loaded and contains no redundant information.

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

Completeness3/5

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

The description is adequate for a simple one-parameter operation, but it omits important context such as whether the API call is asynchronous, whether a precheck is recommended, or how to monitor the restart via related status tools. This leaves gaps for an AI agent planning a restart workflow.

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 fully documents the single parameter serviceGroupInstanceNo with the description 'Cluster instance number', so schema coverage is 100%. The tool description adds no further parameter-level explanation, leaving the baseline score of 3.

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 uses a specific verb 'Perform' and clearly identifies the resource: 'a rolling restart of all nodes in a CDSS cluster'. It distinguishes from sibling tools like ncloud_cdss_restart_all_services and ncloud_cdss_restart_kafka by specifying 'rolling' and 'all nodes'.

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

Usage Guidelines3/5

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

The description implies usage for rolling restarts but does not explicitly state when to choose this tool over alternatives, nor does it mention exclusions or prerequisites. Sibling tools such as ncloud_cdss_rolling_restart_precheck and ncloud_cdss_rolling_restart_status are not referenced.

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

Deploy Server