ncloud-mcp-server

ncloud_update_metrics_group

Idempotent

Update an existing Cloud Insight rule template (metrics group) to adjust metrics, thresholds, and event levels for monitoring.

Instructions

Update an existing Cloud Insight rule template (metrics group).

Input Schema

TableJSON Schema

Name	Required	Description
`prodKey`	Yes	Product key (cw_key) for the target service
`prodType`	No	Product type: system (Ncloud product) or custom (Custom Schema)
`groupDesc`	No	Description (<= 300 chars)
`groupName`	Yes	Name of the metrics group (1-100 chars)
`metricsGroupId`	Yes	Metrics group ID to update
`temporaryGroup`	No	true: create the Event Rule without creating a metrics group (default false)
`metricsGroupItems`	Yes	Metric items (at least one)

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.0.1Oct 7, 2026

addedInput schema / properties / groupDesc

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

changedInput schema / properties / groupName / description

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

removedInput schema / properties / metricList

Removed value: -{
-  "description": "Updated metric 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 / metricsGroupItems

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

addedInput schema / properties / prodKey

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

addedInput schema / properties / prodType

Added value: +{
+  "description": "Product type: system (Ncloud product) or custom (Custom Schema)",
+  "enum": [
+    "system",
+    "custom"
+  ],
+  "type": "string"
+}

addedInput schema / properties / temporaryGroup

Added value: +{
+  "default": false,
+  "description": "true: create the Event Rule without creating a metrics group (default false)",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "metricsGroupId"
-]New value: +[
+  "metricsGroupId",
+  "prodKey",
+  "groupName",
+  "metricsGroupItems"
+]

First observedv1.10.1Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/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 partly covered, but the description adds nothing behavioral: it does not say whether metricsGroupItems replaces the entire item list or is merged, whether existing items require metricGroupItemId, or what happens to existing state. For a mutation of a nested collection these are material omissions.

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?

One short, front-loaded sentence with no padding. It is efficient, though its brevity is partly a symptom of under-specification rather than deliberate economy.

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 rich schema (7 params, nested item array with enums and per-field descriptions) and the idempotent/non-destructive annotations carry most of the load, so the description need not explain return values. Still, the 'rule template' vs 'metrics group' framing and the absence of any statement about update/replace semantics leave a gap for a mutation tool of this complexity.

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 every parameter (including the nested metricsGroupItems sub-properties) is documented in the schema, so the baseline of 3 applies. The description adds no parameter meaning beyond what the schema states.

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 (update) and resource, and the name plus sibling set (ncloud_create_metrics_group, ncloud_delete_metrics_group, ncloud_get_metrics_group) makes the operation unambiguous. However, the parenthetical '(metrics group)' paired with 'Cloud Insight rule template' introduces a mild identity ambiguity — an agent cannot be fully sure whether the object being edited is a rule template or a metrics group.

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?

No guidance on when to use this versus ncloud_create_metrics_group or ncloud_update_rule_group, and no prerequisites (e.g., that the metrics group must already exist and its ID obtained via ncloud_list_metrics_groups). The single sentence offers no usage context at all.

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_metrics_group

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools