Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_metrics_group_force

DestructiveIdempotent

Force delete metrics groups (rule templates) and all related event rules in Naver Cloud Platform. Use groups returned by ncloud_get_rules_by_metrics_group; this action is irreversible.

Instructions

⚠️ Destructive: Force delete rule templates (metrics groups) together with ALL event rules related to them. Pass the groups as returned by ncloud_get_rules_by_metrics_group. This is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupsYesMetrics groups and their related event rules ([{id, ruleGroupItemDtoList}], from ncloud_get_rules_by_metrics_group)
confirmNoMust be true to execute force deletion.
prodKeyYesProduct key (cw_key)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • addedInput schema / properties / groups
      Added value: +{
+  "description": "Metrics groups and their related event rules ([{id, ruleGroupItemDtoList}], from ncloud_get_rules_by_metrics_group)",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "description": "Monitor group or metrics group ID to delete",
+        "type": "string"
+      },
+      "ruleGroupItemDtoList": {
+        "description": "Event Rules related to the group (RuleGroupItemDto[], as returned by ncloud_get_rules_by_metrics_group / ncloud_get_rules_by_monitor_group)",
+        "items": {
+          "additionalProperties": {},
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "id",
+      "ruleGroupItemDtoList"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / metricsGroupId
      Removed value: -{
-  "description": "Metrics group ID whose related rules will be deleted",
-  "type": "string"
-}
    • addedInput schema / properties / prodKey
      Added value: +{
+  "description": "Product key (cw_key)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "metricsGroupId"
-]New value: +[
+  "prodKey",
+  "groups"
+]
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the bar is lower, but the description adds real value beyond them: it discloses the blast radius (all related event rules are destroyed with the group) and that the operation is irreversible. It doesn't discuss the confirm gating or any permission/auth requirement, keeping it below a 5.

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?

Three tight sentences, front-loaded with the destructive warning, then the required input provenance, then irreversibility. Every sentence earns its place with no redundancy.

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 destructive, cascading mutation with no output schema, the description covers danger, blast radius, prerequisite call and irreversibility. The only notable omission is any mention of the confirm flag, but the schema's 100% description coverage for that field compensates.

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 coverage is 100%, so the schema already documents id, ruleGroupItemDtoList, prodKey and the confirm flag. The description only restates the sourcing of the groups array (the get_rules_by_metrics_group reference) and adds nothing about the confirm parameter, so the 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?

States a specific verb (force delete) and resource (rule templates/metrics groups) and explains the cascade: deletion of ALL related event rules. This implicitly distinguishes it from the non-force ncloud_delete_metrics_group, but it never names that sibling, so an agent must infer the difference.

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?

Gives an actionable prerequisite ('pass the groups as returned by ncloud_get_rules_by_metrics_group'), which is clear workflow context. However, it never states when to choose this force variant over ncloud_delete_metrics_group, nor any exclusion conditions.

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