Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_rule_group

DestructiveIdempotent

Delete Cloud Insight event rule groups permanently to stop their monitoring alerts. Requires a product key and rule group IDs, with confirmation for destructive removal.

Instructions

⚠️ Destructive: Delete one or more Cloud Insight event rule groups. This permanently removes the rule groups and stops their monitoring alerts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to execute deletion. If false or omitted, returns a confirmation prompt.
prodKeyYesProduct key (cw_key) the rule groups belong to
ruleGroupIdsYesRule group (Event Rule) IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • addedInput schema / properties / prodKey
      Added value: +{
+  "description": "Product key (cw_key) the rule groups belong to",
+  "type": "string"
+}
    • removedInput schema / properties / ruleGroupId
      Removed value: -{
-  "description": "Rule group ID to delete",
-  "type": "string"
-}
    • addedInput schema / properties / ruleGroupIds
      Added value: +{
+  "description": "Rule group (Event Rule) IDs to delete",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "ruleGroupId"
-]New value: +[
+  "prodKey",
+  "ruleGroupIds"
+]
  2. First observedv1.10.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is partly covered. The description adds meaningful consequence detail beyond the annotations: deletion is permanent and it stops the rule groups' monitoring alerts, which is the key operational impact an agent should surface.

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 compact clauses with the destructive warning front-loaded via the ⚠️ marker, and every sentence carries information. It could be marginally tighter but there is no filler.

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 delete with full schema coverage, an output schema unnecessary, and annotations covering idempotency/destructiveness, the description supplies adequate purpose and consequence context. The only gap is routing guidance to the singular sibling.

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 prodKey, ruleGroupIds, and the confirm flag are fully documented in the schema. The description adds nothing about parameters (notably omitting the confirm=true gate), 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 (Delete) and resource (Cloud Insight event rule groups) with a clear scope hint ('one or more') that implicitly separates it from the singular sibling ncloud_delete_rule_group_by_id. It never names that sibling, so the differentiation is inferred rather than explicit.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the closest alternative (ncloud_delete_rule_group_by_id) is never mentioned. The phrase 'one or more' weakly implies batch usage but the agent must infer when to pick this tool over its per-ID sibling.

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