ncloud-mcp-server

ncloud_create_rule_group

Create a Cloud Insight event rule group by linking monitor targets and metric templates, with optional notification recipients for monitoring alerts.

Instructions

Create a new Cloud Insight event rule group for monitoring alerts. Links existing monitor groups (targets) and metrics groups (rule templates) and optional notification recipients.

Input Schema

TableJSON Schema

Name	Required	Description
`dryRun`	No	If true, returns a preview without creating the rule group (default: false)
`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)
`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.

Changed13 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": "List of rule configurations defining alert conditions",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "aggregation": {
-        "description": "Aggregation type (default: AVG)",
-        "enum": [
-          "AVG",
-          "MIN",
-          "MAX",
-          "SUM",
-          "COUNT"
-        ],
-        "type": "string"
-      },
-      "condition": {
-        "description": "Threshold condition (GT: >, GTE: >=, LT: <, LTE: <=, EQ: ==)",
-        "enum": [
-          "GT",
-          "GTE",
-          "LT",
-          "LTE",
-          "EQ"
-        ],
-        "type": "string"
-      },
-      "duration": {
-        "description": "Duration in minutes before triggering alert",
-        "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: -"Name of the rule group"New value: +"Name of the rule group (1-1000 chars)"

removedInput schema / properties / metricsGroupId

Removed value: -{
-  "description": "Metrics group ID (rule template) to apply",
-  "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": "Monitor group ID (target group) to monitor",
-  "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"
+}

removedInput schema / properties / recipientNotification

Removed value: -{
-  "description": "Notification recipients for alerts",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "notificationType": {
-        "description": "Notification type",
-        "enum": [
-          "EMAIL",
-          "SMS",
-          "WEBHOOK"
-        ],
-        "type": "string"
-      },
-      "recipient": {
-        "description": "Notification recipient (email, phone, or webhook URL)",
-        "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"
+}

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: -[
-  "groupName",
-  "prodKey",
-  "metricsGroupId",
-  "monitorGroupId",
-  "cfgRuleList"
-]New value: +[
+  "prodKey",
+  "groupName",
+  "metricsGroupKey",
+  "monitorGroupKey"
+]

First observedv1.10.1Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The destructiveHint=false annotation covers the safety profile, and the description consistently frames this as a creation that 'links existing' groups (a prerequisite insight). However it does not mention the dryRun preview option, permission requirements, or that the required monitor/metrics groups must already exist, which the schema does not state either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the core action, no filler. Efficient for the amount of information conveyed, though it could have used the second sentence to route to alternatives rather than repeat the linking behavior.

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?

There is no output schema, and this is a 10-parameter write operation with nested objects. The description gives the essential intent but omits the dryRun preview (a useful safety affordance), suspendRuleItems, and ASG policy behavior, which an agent must reconstruct from the schema alone.

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 schema already documents all 10 parameters including dryRun, suspendRuleItems, and asgPolicyList. The description only restates the three conceptual inputs (monitor groups, metrics groups, optional notification recipients), adding no syntax or constraint detail beyond the schema. Baseline 3 applies.

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?

Specific verb+resource: 'Create a new Cloud Insight event rule group for monitoring alerts,' which clearly distinguishes it from update_rule_group, get_rule_group, and create_rule_directly. It also names what the group links. It stops short of explicitly contrasting with the similar-sounding create_rule_directly sibling.

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 'for monitoring alerts' implies the context, and the linking of existing monitor/metrics groups implies the operation requires prior entities, but there is no explicit when-to-use vs when-not guidance or named alternative (e.g. create_rule_directly, copy_rule_group).

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

Deploy Server

ncloud_create_rule_group

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools