Skip to main content
Glama
Sign In
ncloud-mcp-server

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_metrics_group

DestructiveIdempotent

Delete one or more Cloud Insight rule templates (metrics groups) for a product key using IDs; confirmation must be true to execute.

Instructions

⚠️ Destructive: Delete one or more Cloud Insight rule templates (metrics groups).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prodKey": "<prodKey>",
      "metricsGroupIds": "<metricsGroupIds>"
    },
    "name": "ncloud_delete_metrics_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute deletion.
prodKeyYesProduct key (cw_key) the metrics groups belong to
metricsGroupIdsYesMetrics group IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description's '⚠️ Destructive' merely restates that. It adds the clarification that a metrics group is a Cloud Insight rule template, but omits the schema's confirm=true gate and says nothing about irreversibility or what happens to attached rules.

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?

One short sentence, warning front-loaded, zero filler or redundancy.

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 destructive, batch-capable delete tool with no output schema, the description leaves the confirmation requirement and the sibling-tool choice to be inferred from the schema and tool list. It is minimally adequate but not self-sufficient.

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, metricsGroupIds, and the confirm flag are already fully documented in the schema. The description adds no parameter-level meaning, 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 rule templates / metrics groups) with batch scope ('one or more'). It does not distinguish itself from close siblings such as ncloud_delete_metrics_group_by_id or ncloud_delete_metrics_group_force, but the core action is unambiguous.

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 when-to-use guidance, no preconditions, and no mention of the alternative deletion tools (by-id, force). An agent has no signal for choosing between the three delete variants.

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