Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_apply_config_group

Idempotent

Apply a config group to a CDSS cluster by providing its number, Kafka version code, and target cluster instance to enforce matching configuration.

Instructions

Apply a Config Group to a CDSS cluster. The cluster must run the same Kafka version as the group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configGroupNoYesConfig group number to apply (from ncloud_cdss_list_config_groups)
kafkaVersionCodeYesKafka version code of the group (from ncloud_cdss_get_kafka_versions)
serviceGroupInstanceNoYesTarget cluster instance number (from ncloud_cdss_list_clusters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • changedInput schema / properties / configGroupNo / description
      Previous value: -"Config group number to apply"New value: +"Config group number to apply (from ncloud_cdss_list_config_groups)"
    • addedInput schema / properties / kafkaVersionCode
      Added value: +{
+  "description": "Kafka version code of the group (from ncloud_cdss_get_kafka_versions)",
+  "type": "number"
+}
    • changedInput schema / properties / serviceGroupInstanceNo / description
      Previous value: -"Target cluster instance number"New value: +"Target cluster instance number (from ncloud_cdss_list_clusters)"
    • changedInput schema / properties / serviceGroupInstanceNo / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / required
      Previous value: -[
-  "configGroupNo",
-  "serviceGroupInstanceNo"
-]New value: +[
+  "configGroupNo",
+  "kafkaVersionCode",
+  "serviceGroupInstanceNo"
+]
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the version-compatibility constraint but does not disclose other behavioral effects, such as whether the apply triggers a restart or is an asynchronous 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 concise sentences with no wasted words. The main action comes first, and the essential prerequisite is stated immediately after.

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

Completeness4/5

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

For a simple three-parameter operation with annotations covering idempotency and non-destructiveness, the description is largely complete. A minor gap is the lack of any mention of what the API returns or whether the operation is asynchronous, but no output schema exists to require that explanation.

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 schema has 100% parameter description coverage, with each parameter explaining its meaning and source. The description adds no additional parameter semantics, so the 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 uses a specific verb and resource: "Apply a Config Group to a CDSS cluster." This clearly identifies the operation and distinguishes it from sibling tools like create/delete/change config group or cluster creation.

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?

It states a key precondition: the cluster must run the same Kafka version as the group. However, it does not explicitly describe when to use this tool versus alternatives, nor does it state when not to use it.

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