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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_monitor_group_force

DestructiveIdempotent

Force delete all event rules associated with a monitoring target group, permanently removing them. Requires explicit confirmation to execute.

Instructions

⚠️ Destructive: Force delete ALL event rules associated with a specific monitoring target 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": {
      "monitorGroupId": "<monitorGroupId>"
    },
    "name": "ncloud_delete_monitor_group_force"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute force deletion.
monitorGroupIdYesMonitor group ID whose related rules will be deleted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

The description goes beyond the destructiveHint annotation by explicitly stating 'This is irreversible' and emphasizing 'ALL' event rules, which communicates the full scope of impact. It also adds a warning emoji, reinforcing the destructive nature.

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, concise sentence that front-loads the destructive warning. It contains no fluff or redundant information, earning its place with each word.

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 deletion tool, the description adequately communicates the target (all event rules for a monitor group), the irreversibility, and the force nature. It doesn't explicitly state that the monitor group itself is not deleted, but the phrasing implies that. No output schema exists, so return-value documentation is not required.

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 coverage is 100%, so the description doesn't need to explain parameter meaning. The description does not add any parameter-level details beyond what the schema provides, which is appropriate given the complete schema coverage.

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 tool's action: 'Force delete ALL event rules associated with a specific monitoring target group.' It specifies the resource (event rules of a monitoring target group), scope (ALL), and nature (force delete), effectively distinguishing it from other deletion tools like ncloud_delete_monitor_group.

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 a use case (bulk removal of event rules for a monitoring group) but does not explicitly state when to use this over alternatives or provide any exclusions. No comparison to sibling tools like ncloud_delete_monitor_group or ncloud_remove_resource_from_rules is provided.

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