ncloud-mcp-server

ncloud_update_rule_group

Idempotent

Update an existing Cloud Insight event rule group's monitored targets, metric templates, notifications, or suspended rules; pass the current group name because it cannot change.

Instructions

Update an existing Cloud Insight event rule group. groupName cannot be changed — pass the current name.

Input Schema

TableJSON Schema

Name	Required	Description
`prodKey`	Yes	Product key (cw_key) for the target service
`groupDesc`	No	Description (<= 300 chars)
`groupName`	Yes	Name of the rule group (1-1000 chars)
`ruleGroupId`	Yes	Rule group (Event Rule) ID to update
`asgPolicyList`	No	Auto Scaling group policies
`metricsGroupKey`	Yes	Metrics group (rule template) IDs to apply (at least one)
`monitorGroupKey`	Yes	Monitor group (target group) IDs to monitor (at least one)
`suspendRuleItems`	No	Rule items to suspend ([{resourceId, metricGroupItemId}])
`recipientNotifications`	No	Notification recipient groups
`personalNotificationRecipients`	No	Personal notification recipients

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv2.0.1Oct 7, 2026

addedInput schema / properties / asgPolicyList

Added value: +{
+  "description": "Auto Scaling group policies",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "autoScalingGroupNo": {
+        "description": "Auto Scaling group number",
+        "type": "number"
+      },
+      "autoScalingPolicyNo": {
+        "description": "Auto Scaling policy number",
+        "type": "number"
+      },
+      "policyName": {
+        "description": "Auto Scaling policy name",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / cfgRuleList

Removed value: -{
-  "description": "Updated rule configurations",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "aggregation": {
-        "description": "Aggregation type",
-        "enum": [
-          "AVG",
-          "MIN",
-          "MAX",
-          "SUM",
-          "COUNT"
-        ],
-        "type": "string"
-      },
-      "condition": {
-        "description": "Threshold condition",
-        "enum": [
-          "GT",
-          "GTE",
-          "LT",
-          "LTE",
-          "EQ"
-        ],
-        "type": "string"
-      },
-      "duration": {
-        "description": "Duration in minutes",
-        "type": "number"
-      },
-      "eventLevel": {
-        "description": "Event severity level",
-        "enum": [
-          "CRITICAL",
-          "WARNING",
-          "INFO"
-        ],
-        "type": "string"
-      },
-      "metricGroupItemId": {
-        "description": "Metric item ID",
-        "type": "string"
-      },
-      "threshold": {
-        "description": "Threshold value",
-        "type": "number"
-      }
-    },
-    "required": [
-      "metricGroupItemId",
-      "condition",
-      "threshold",
-      "duration",
-      "eventLevel"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / groupDesc

Added value: +{
+  "description": "Description (<= 300 chars)",
+  "type": "string"
+}

changedInput schema / properties / groupName / description

Previous value: -"New name for the rule group"New value: +"Name of the rule group (1-1000 chars)"

removedInput schema / properties / metricsGroupId

Removed value: -{
-  "description": "New metrics group ID",
-  "type": "string"
-}

addedInput schema / properties / metricsGroupKey

Added value: +{
+  "description": "Metrics group (rule template) IDs to apply (at least one)",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

removedInput schema / properties / monitorGroupId

Removed value: -{
-  "description": "New monitor group ID",
-  "type": "string"
-}

addedInput schema / properties / monitorGroupKey

Added value: +{
+  "description": "Monitor group (target group) IDs to monitor (at least one)",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / personalNotificationRecipients

Added value: +{
+  "description": "Personal notification recipients",
+  "items": {
+    "$ref": "#/properties/recipientNotifications/items"
+  },
+  "type": "array"
+}

addedInput schema / properties / prodKey

Added value: +{
+  "description": "Product key (cw_key) for the target service",
+  "type": "string"
+}

removedInput schema / properties / recipientNotification

Removed value: -{
-  "description": "Updated notification recipients",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "notificationType": {
-        "description": "Notification type",
-        "enum": [
-          "EMAIL",
-          "SMS",
-          "WEBHOOK"
-        ],
-        "type": "string"
-      },
-      "recipient": {
-        "description": "Notification recipient",
-        "type": "string"
-      }
-    },
-    "required": [
-      "notificationType",
-      "recipient"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / recipientNotifications

Added value: +{
+  "description": "Notification recipient groups",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "enableNotiWhenEventClose": {
+        "description": "Send a notification when the event closes",
+        "type": "boolean"
+      },
+      "groupName": {
+        "description": "Notification recipient group name",
+        "type": "string"
+      },
+      "groupNum": {
+        "description": "Notification recipient group number",
+        "type": "number"
+      },
+      "notifyTypes": {
+        "description": "Notification methods (SMS, EMAIL)",
+        "items": {
+          "enum": [
+            "SMS",
+            "EMAIL"
+          ],
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "reminderTime": {
+        "description": "Reminder interval in minutes (5-720)",
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / ruleGroupId / description

Previous value: -"Rule group ID to update"New value: +"Rule group (Event Rule) ID to update"

addedInput schema / properties / suspendRuleItems

Added value: +{
+  "description": "Rule items to suspend ([{resourceId, metricGroupItemId}])",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "metricGroupItemId": {
+        "description": "Metric item ID",
+        "type": "string"
+      },
+      "resourceId": {
+        "description": "Monitoring target ID",
+        "type": "string"
+      }
+    },
+    "required": [
+      "resourceId",
+      "metricGroupItemId"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "ruleGroupId"
-]New value: +[
+  "ruleGroupId",
+  "prodKey",
+  "groupName",
+  "metricsGroupKey",
+  "monitorGroupKey"
+]

First observedv1.10.1Jul 29, 2026

TDQS

B3.3/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, so the safety profile is covered. The description adds one genuinely useful behavioral fact — groupName is immutable and must be the current name — but says nothing about how omitted optional fields are handled (merge vs replace), which matters for a 10-param update.

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 sentences, zero waste, and the one non-obvious constraint is isolated in its own sentence. Nothing to trim.

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 an update tool with ten parameters, many optional and some nested, the description is thin. It states purpose and one constraint, but leaves partial-update semantics unaddressed; with 100% schema coverage and safety annotations, this is adequate but not complete.

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%, so the baseline is 3. The description adds the immutability constraint on groupName beyond the schema's '1-1000 chars' note, but gives no semantic help for the other nine parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Update an existing Cloud Insight event rule group.' The verb clearly distinguishes it from siblings like ncloud_create_rule_group, ncloud_delete_rule_group, and ncloud_get_rule_group, though it never names those alternatives explicitly.

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?

Provides no when-to-use guidance or routing against alternatives such as ncloud_copy_rule_group or ncloud_create_rule_directly. The groupName note is a behavioral constraint, not usage guidance, so the agent receives no help choosing between this and its rule-group siblings.

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

Deploy Server

ncloud_update_rule_group

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools