ncloud-gov-mcp-server

ncloud_delete_metrics_group_force

DestructiveIdempotent

Force delete all event rules associated with a specific metrics group. Irreversible action that removes rules permanently.

Instructions

⚠️ Destructive: Force delete ALL event rules associated with a specific rule template (metrics group). This is irreversible.

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

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to execute force deletion.
`metricsGroupId`	Yes	Metrics group ID whose related rules will be deleted

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds useful context beyond the annotations: it emphasizes irreversibility and the cascade deletion of ALL event rules. It does not contradict the destructiveHint or idempotentHint annotations. It lacks details on permissions or failure modes but is still informative.

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 sentence with a front-loaded warning symbol, clearly conveying the destructive nature and scope. There is no redundant information or 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 operation, the description covers the essential behavior: it deletes all associated rules and is irreversible. The schema and annotations fill in parameter details and safety hints. It could be slightly more complete by clarifying when the confirm parameter is required, but that is already captured in the schema.

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?

The input schema already provides full descriptions for both parameters (metricsGroupId and confirm), with 100% coverage. The description itself adds no additional parameter semantics, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action: force delete ALL event rules associated with a metrics group, and notes it is irreversible. This distinguishes it from sibling tools like ncloud_delete_metrics_group (non-force) and ncloud_delete_rule_group_by_id.

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?

The description implies this tool is used when you want to delete a metrics group along with all its event rules, but it does not explicitly explain when to choose this over the non-force ncloud_delete_metrics_group or when not to use it. No alternatives are named.

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

Deploy Server