ncloud-mcp-server

ncloud_delete_metrics_group_by_id

DestructiveIdempotent

Delete a Cloud Insight metrics group by product key and metrics group ID. Set confirm to true to execute this destructive operation.

Instructions

⚠️ Destructive: Delete a Cloud Insight rule template by product key and metrics group ID.

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>",
      "metricsGroupId": "<metricsGroupId>"
    },
    "name": "ncloud_delete_metrics_group_by_id"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to execute deletion.
`prodKey`	Yes	Product key (cw_key)
`metricsGroupId`	Yes	Metrics group ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description's 'Destructive' warning merely duplicates the destructiveHint annotation. It adds no additional behavioral context such as irreversibility, cascading effects on related resources, or confirmation requirements. With annotations already covering safety, the description contributes minimal extra transparency.

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?

The description is a single, front-loaded sentence that includes a warning icon and clearly states the action and key parameters. No superfluous content, making it highly efficient for an agent to parse quickly.

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 simple delete operation with annotations covering destructive behavior and schema covering parameters, the description is minimally adequate. However, it lacks context about related tools, the relationship between rule templates and metrics groups, and any side effects beyond the deletion itself, which limits its completeness.

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 parameters. The description's mention of 'product key and metrics group ID' aligns with the schema but adds no new semantic detail. The confirm parameter's crucial requirement ('Must be true to execute deletion') is only in the schema, not echoed in the description.

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?

The description clearly states the action (Delete), the resource type (Cloud Insight rule template), and the identifying fields (product key and metrics group ID). It is specific and distinguishes itself from the basic 'delete_metrics_group' by including 'by_id', though it could more explicitly mention related force-delete variants.

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 is provided regarding when to use this tool versus alternatives like ncloud_delete_metrics_group_force or ncloud_delete_metrics_group. The description does not mention prerequisites, conditions, or exclusions, leaving the agent to infer context from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server