Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_restart_kafka_per_node

Idempotent

Restart Kafka on selected CDSS cluster nodes by specifying server instance numbers, enabling targeted recovery or configuration updates without disrupting the entire cluster.

Instructions

Restart Kafka on one or more specific nodes in a CDSS cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
computeInstanceNoListYesNode server instance numbers to restart (from ncloud_cdss_list_nodes)
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • removedInput schema / properties / computeInstanceNo
      Removed value: -{
-  "description": "Node compute instance number to restart",
-  "type": "string"
-}
    • addedInput schema / properties / computeInstanceNoList
      Added value: +{
+  "description": "Node server instance numbers to restart (from ncloud_cdss_list_nodes)",
+  "items": {
+    "type": [
+      "number",
+      "string"
+    ]
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "computeInstanceNo"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "computeInstanceNoList"
+]
  2. First observedv1.10.1

TDQS

A3.5/5.0
Behavior2/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 no behavioral context about asynchronous operation, potential downtime, or how to monitor completion—it only restates scope rather than behavior.

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?

Single sentence with zero filler; action and scope are front-loaded and 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?

Adequate for a simple restart operation with full schema coverage and safety annotations, but lacks guidance on asynchronous operation status checking, effect on cluster availability, and does not explicitly distinguish from ncloud_cdss_restart_all_services.

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%: computeInstanceNoList is described as node instance numbers from ncloud_cdss_list_nodes, and serviceGroupInstanceNo as cluster instance number. The description adds no additional parameter semantics beyond what the schema already provides.

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?

Description uses specific verb 'Restart', resource 'Kafka', and scope 'one or more specific nodes in a CDSS cluster'. It clearly differentiates from sibling tools like ncloud_cdss_restart_kafka and ncloud_cdss_rolling_restart by emphasizing per-node targeting.

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 phrase 'one or more specific nodes' implies targeted node-level restart, but it does not explicitly name alternatives or state when not to use it. An agent must infer from sibling names that cluster-wide restart operations are separate.

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