ncloud-mcp-server

ncloud_create_rule_directly

Create Cloud Insight event rules by specifying monitor targets and metric templates inline, eliminating the need for pre-created monitor and metrics groups.

Instructions

Create a Cloud Insight event rule by directly specifying the monitor group (targets) and metrics group (rule template) inline, without pre-created groups.

Input Schema

TableJSON Schema

Name	Required	Description
`prodKey`	Yes	Product key (cw_key)
`groupDesc`	No	Description (<= 300 chars)
`groupName`	Yes	Name of the rule group (1-100 chars)
`asgPolicys`	No	VPC Auto Scaling group policies
`cfTriggers`	No	Cloud Functions trigger names
`metricsGroup`	Yes	Metrics group definition (CreateOrUpdateMetricsGrpDto)
`monitorGroup`	Yes	Monitor group definition (MonitorGrpDto)
`classicAsgPolicys`	No	Classic Auto Scaling group policies
`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 / asgPolicys

Added value: +{
+  "description": "VPC 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"
+}

addedInput schema / properties / cfTriggers

Added value: +{
+  "description": "Cloud Functions trigger names",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / cfgRuleList

Removed value: -{
-  "description": "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 / classicAsgPolicys

Added value: +{
+  "description": "Classic Auto Scaling group policies",
+  "items": {
+    "$ref": "#/properties/asgPolicys/items"
+  },
+  "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-100 chars)"

addedInput schema / properties / metricsGroup

Added value: +{
+  "additionalProperties": false,
+  "description": "Metrics group definition (CreateOrUpdateMetricsGrpDto)",
+  "properties": {
+    "groupDesc": {
+      "description": "Description (<= 300 chars)",
+      "type": "string"
+    },
+    "groupName": {
+      "description": "Name of the metrics group (1-100 chars)",
+      "type": "string"
+    },
+    "metricsGroupItems": {
+      "description": "Metric items (at least one)",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "calculation": {
+            "description": "Aggregation of the metric",
+            "enum": [
+              "COUNT",
+              "SUM",
+              "MAX",
+              "MIN",
+              "AVG"
+            ],
+            "type": "string"
+          },
+          "condition": {
+            "description": "Threshold operator (LT, LE, EQ, GE, GT)",
+            "enum": [
+              "LT",
+              "LE",
+              "EQ",
+              "GE",
+              "GT"
+            ],
+            "type": "string"
+          },
+          "desc": {
+            "description": "Metric description",
+            "type": "string"
+          },
+          "dimensions": {
+            "description": "Dimension filters, e.g. [{dim:\"type\", val:\"svr\"}]",
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "dim": {
+                  "description": "Dimension name defined in the schema (e.g. \"type\")",
+                  "type": "string"
+                },
+                "val": {
+                  "description": "Dimension value (e.g. \"svr\")",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "dim",
+                "val"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "duration": {
+            "description": "Duration (>= 1)",
+            "type": "number"
+          },
+          "eventLevel": {
+            "description": "Event level",
+            "enum": [
+              "INFO",
+              "WARNING",
+              "CRITICAL"
+            ],
+            "type": "string"
+          },
+          "metric": {
+            "description": "Metric name (e.g. avg_cpu_used_rto)",
+            "type": "string"
+          },
+          "metricGroupItemId": {
+            "description": "Metric group item ID (when updating an existing item)",
+            "type": "string"
+          },
+          "threshold": {
+            "description": "Threshold value",
+            "type": "number"
+          }
+        },
+        "required": [
+          "metric",
+          "eventLevel",
+          "condition",
+          "calculation",
+          "duration",
+          "threshold"
+        ],
+        "type": "object"
+      },
+      "minItems": 1,
+      "type": "array"
+    },
+    "prodKey": {
+      "description": "Product key (cw_key) for the target service",
+      "type": "string"
+    },
+    "prodType": {
+      "description": "Product type: system (Ncloud product) or custom (Custom Schema)",
+      "enum": [
+        "system",
+        "custom"
+      ],
+      "type": "string"
+    },
+    "temporaryGroup": {
+      "default": false,
+      "description": "true: create the Event Rule without creating a metrics group (default false)",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "prodKey",
+    "groupName",
+    "metricsGroupItems"
+  ],
+  "type": "object"
+}

addedInput schema / properties / monitorGroup

Added value: +{
+  "additionalProperties": false,
+  "description": "Monitor group definition (MonitorGrpDto)",
+  "properties": {
+    "groupDesc": {
+      "description": "Description of the monitor group",
+      "type": "string"
+    },
+    "groupName": {
+      "description": "Name of the monitor group",
+      "type": "string"
+    },
+    "monitorGroupItemList": {
+      "description": "Monitoring targets ([{resourceId, nrn?}])",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "nrn": {
+            "description": "Resource NRN (Resource Manager)",
+            "type": "string"
+          },
+          "resourceId": {
+            "description": "Monitoring target resource ID (e.g. server instance number)",
+            "type": "string"
+          },
+          "resourceName": {
+            "description": "Resource name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "resourceId"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "prodKey": {
+      "description": "Product key (cw_key) for the target service",
+      "type": "string"
+    },
+    "prodName": {
+      "description": "Product name",
+      "type": "string"
+    },
+    "temporaryGroup": {
+      "description": "true: create the Event Rule without creating a monitor group",
+      "type": "boolean"
+    },
+    "type": {
+      "description": "Target group type: NORMAL (default) or ASG (Auto Scaling Group)",
+      "enum": [
+        "NORMAL",
+        "ASG"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "prodKey",
+    "monitorGroupItemList"
+  ],
+  "type": "object"
+}

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",
-  "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"
+}

removedInput schema / properties / resourceList

Removed value: -{
-  "description": "Array of resource dimension objects to monitor",
-  "items": {
-    "additionalProperties": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

changedInput schema / required

Previous value: -[
-  "groupName",
-  "prodKey",
-  "resourceList",
-  "cfgRuleList"
-]New value: +[
+  "prodKey",
+  "groupName",
+  "monitorGroup",
+  "metricsGroup"
+]

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?

Only annotation is destructiveHint=false, so the description carries most of the burden. It discloses that the monitor/metrics groups are supplied inline rather than pre-created (a meaningful behavioral trait), but does not state whether this creates the groups as side effects, permission requirements, or validation constraints. Partial coverage.

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?

A single front-loaded sentence that states the action, the mechanism, and the constraint with no filler. Efficient, though slightly terse given the tool's complexity.

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 a complex mutation tool with 10 params, deep nested objects, and only one weak annotation, the description is thin – it omits the temporaryGroup semantics, notification behavior, and the multi-entity creation model. The rich schema compensates for parameter detail but not for behavioral context.

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. The description adds marginal value by glossing monitorGroup as 'targets' and metricsGroup as 'rule template', clarifying their roles, but gives no syntax or relationship detail beyond that. Baseline 3.

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+resource ('Create a Cloud Insight event rule') and identifies its differentiator: specifying the monitor group and metrics group inline 'without pre-created groups'. This separates it from sibling creators like create_monitor_group/create_metrics_group, though it does not name them explicitly.

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 'without pre-created groups' implies the condition under which this tool is preferred, but it never states the alternative tool or the when-not-to-use case explicitly. Usage is inferable but not spelled out.

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_directly

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools