ncloud-mcp-server

ncloud_cdss_restart_all_services

Idempotent

Restart all services in a CDSS cluster by providing the cluster instance number. Covers Kafka, ZooKeeper, and CMAK.

Instructions

Restart all services (Kafka + ZooKeeper + CMAK) 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_restart_all_services"
  }
}

Input Schema

Name	Required	Description	Default
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds valuable context by listing the affected components (Kafka, ZooKeeper, CMAK), which is not conveyed by the annotations alone. However, it does not disclose operational impact such as potential downtime or whether the restart is all-at-once versus rolling.

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 concise sentence that conveys the essential information without any filler. Every word earns its place.

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?

For a simple tool with one parameter and no output schema, the description provides the core functionality. However, given the presence of sibling tools like ncloud_cdss_rolling_restart and ncloud_cdss_restart_kafka_per_node, some guidance on when to use this full restart versus those alternatives would complete the picture.

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% because the single parameter 'serviceGroupInstanceNo' has a description ('Cluster instance number'). The description does not add any additional parameter semantics, but the schema already sufficiently documents this parameter.

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 ('Restart'), the scope ('all services'), and the specific components ('Kafka + ZooKeeper + CMAK') in a CDSS cluster. This differentiates it from sibling tools like ncloud_cdss_restart_kafka and ncloud_cdss_restart_cmak, which target individual services.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It does not mention why one would choose this over the rolling restart or per-node restart tools, nor does it state any prerequisites or exclusions.

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

Deploy Server