ncloud-gov-mcp-server

ncloud_delete_monitor_group

DestructiveIdempotent

Permanently remove a Cloud Insight monitoring target group by providing its unique ID. Confirmation is required to execute the deletion.

Instructions

⚠️ Destructive: Delete a Cloud Insight monitoring target group. This will permanently remove the group.

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": {
      "monitorGroupId": "<monitorGroupId>"
    },
    "name": "ncloud_delete_monitor_group"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to execute deletion.
`monitorGroupId`	Yes	Monitor group ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations already provide destructiveHint=true, and the description reinforces this with 'Destructive' and 'permanently remove', adding the irreversible consequence. However, it omits the confirm parameter's mandatory role and doesn't mention idempotency or any other side effects, so it adds modest context beyond annotations.

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?

The description is a single declarative sentence with a warning prefix, making it efficient and front-loaded. However, the 'Destructive' warning partially duplicates the annotation, but it is still concise and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is very brief and omits the safety confirmation requirement (confirm=true), which is critical for a destructive operation. It also doesn't mention that the operation is irreversible beyond 'permanently remove', nor does it reference the force variant, leaving the agent without key execution context despite the simple tool shape.

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 describes both parameters (confirm must be true, monitorGroupId is the ID to delete) with 100% coverage, so the description adds no additional parameter detail. Baseline of 3 is appropriate.

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') and the resource ('Cloud Insight monitoring target group'), adding that removal is permanent. It differentiates from read/create/update tools but not from the sibling ncloud_delete_monitor_group_force, so it falls slightly short of full differentiation.

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 given for when to use this tool versus alternatives such as ncloud_delete_monitor_group_force or when not to use it. The description only warns of destructiveness without explaining the confirm parameter or any preconditions, leaving the agent without selection criteria.

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

Deploy Server