Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_upgrade_version

Upgrade Kafka version of a CDSS cluster after running precheck. Specify cluster, target version, and config group to apply the upgrade.

Instructions

Upgrade the Kafka version of a CDSS cluster. Run ncloud_cdss_upgrade_precheck first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upgradeConfigGroupNoYesConfig group number for the target version (from ncloud_cdss_list_config_groups)
serviceGroupInstanceNoYesCluster instance number
upgradeKafkaVersionCodeYesTarget Kafka version code (from ncloud_cdss_get_kafka_versions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • removedInput schema / properties / configGroupNo
      Removed value: -{
-  "description": "Config group number for the new version",
-  "type": "string"
-}
    • removedInput schema / properties / kafkaVersionCode
      Removed value: -{
-  "description": "Target Kafka version code",
-  "type": "string"
-}
    • addedInput schema / properties / upgradeConfigGroupNo
      Added value: +{
+  "description": "Config group number for the target version (from ncloud_cdss_list_config_groups)",
+  "type": "number"
+}
    • addedInput schema / properties / upgradeKafkaVersionCode
      Added value: +{
+  "description": "Target Kafka version code (from ncloud_cdss_get_kafka_versions)",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "kafkaVersionCode"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "upgradeKafkaVersionCode",
+  "upgradeConfigGroupNo"
+]
  2. First observedv1.10.1

TDQS

A3.7/5.0
Behavior2/5

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

With empty annotations and no output schema, the description carries the full burden of behavioral disclosure. It only says 'upgrade' without mentioning potential downtime, service impact, irreversibility, or how to monitor progress (e.g., ncloud_cdss_upgrade_status). The precheck hint is the only behavioral context, which is insufficient for a mutating operation.

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?

Two compact sentences with no filler. The main action and the critical prerequisite are both front-loaded. Every word contributes to the agent's understanding.

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 gives the essential action and prerequisite, and the schema documents all three required parameters. However, it omits expected outcomes, side effects, and how to follow up on the upgrade (e.g., via ncloud_cdss_upgrade_status). For a state-changing operation with no output schema and empty annotations, this is a noticeable gap.

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%, and each parameter's description already names its source (e.g., 'from ncloud_cdss_list_config_groups'). The tool description adds no extra parameter-level meaning beyond the schema, so the baseline of 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 Kafka version') and the specific resource ('a CDSS cluster'). It is distinct from sibling tools like ncloud_cdss_upgrade_precheck and ncloud_cdss_upgrade_status, and names the precheck tool explicitly, making the tool's role unambiguous.

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 gives an explicit prerequisite: 'Run ncloud_cdss_upgrade_precheck first.' This tells an agent the required preceding step. It does not discuss when not to use the tool or alternatives, but the context that a precheck must run first is clear and actionable.

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