ncloud-gov-mcp-server

ncloud_gtm_delete_profile

DestructiveIdempotent

Permanently delete a Global Traffic Manager profile by domain ID. Set confirm=true to execute.

Instructions

⚠️ Destructive: Permanently delete a Global Traffic Manager profile (domain). 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_gtm_delete_profile"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds valuable context by noting the deletion is permanent and requires an explicit confirm flag. It does not contradict annotations and provides extra safety-relevant behavior beyond the structured fields.

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 two short sentences with no filler, front-loading the destructive warning and clearly stating the required action. Every word contributes to understanding the tool's purpose and safety requirement.

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 simple delete tool with two parameters and strong annotations, the description is largely complete. It covers the destructive nature, permanence, and confirm guard. It could mention any cascading effects or return behavior, but these are not necessary given the low complexity and schema coverage.

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%, with both parameters well-documented. The description restates the confirm requirement but adds little beyond the schema. This matches the baseline of 3 when the schema already explains parameters fully.

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 uses a specific verb ('delete') and specific resource ('Global Traffic Manager profile (domain)'), clearly distinguishing it from sibling tools like ncloud_gtm_delete_policy or ncloud_gtm_update_profile. The phrase 'Permanently delete' reinforces the exact action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly frames this as a destructive operation and provides a key usage instruction: 'Set confirm=true to execute.' This gives the agent clear context for when to invoke it, though it does not explicitly mention alternatives or when not to use it.

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

Deploy Server