ncloud-gov-mcp-server

ncloud_dns_delete_domain

DestructiveIdempotent

Permanently delete a Global DNS domain and all its records. Requires confirm=true to execute the destructive action.

Instructions

⚠️ Destructive: Permanently delete a Global DNS domain. All records under this domain will be removed. Set confirm=true to execute.

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": {
      "domainId": "<domainId>"
    },
    "name": "ncloud_dns_delete_domain"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`domainId`	Yes	Domain ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description goes beyond the destructiveHint annotation by specifying that deletion is permanent, cascades to all records, and requires confirm=true to execute. The warning emoji and explicit consequences provide valuable behavioral disclosure that annotations do not cover.

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, information-dense sentence. It front-loads the destructive warning, clearly states the action, consequence, and required confirmation flag, with no unnecessary words.

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

Completeness5/5

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

For a destructive delete tool with annotations covering idempotency and destructiveness, the description effectively conveys the essential context: permanence, cascading deletion, and confirmation requirement. No output schema exists, so no return-value explanation is needed.

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%, and the description adds no extra parameter information beyond what the schema already states. The mention of confirm=true is redundant with the schema's confirm description, so the baseline of 3 applies.

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 action: 'Permanently delete a Global DNS domain.' It specifies the resource and distinguishes from record-level operations by noting all records under the domain will be removed, differentiating it from sibling tools like ncloud_dns_delete_records.

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 when to use this tool (to delete an entire DNS domain) but does not explicitly mention alternatives or when-not to use it. It lacks a direct reference to sibling tools for deleting individual records, leaving the guidance implied rather than explicit.

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

Deploy Server