ncloud-gov-mcp-server

ncloud_delete_nat_gateway

DestructiveIdempotent

Permanently delete a NAT Gateway instance. Requires explicit confirmation by setting confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a NAT Gateway instance. 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": {
      "natGatewayInstanceNo": "<natGatewayInstanceNo>"
    },
    "name": "ncloud_delete_nat_gateway"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute the destructive operation
`natGatewayInstanceNo`	Yes	NAT Gateway instance number to delete
`returnPublicIpInstance`	No	Also return (release) the public IP instance assigned to the public NAT Gateway. Default: true

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 that the deletion is permanent and requires confirm=true to execute, providing useful behavioral context beyond the annotation. This does not contradict any annotation.

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, front-loaded sentence with a warning emoji, effectively communicating the destructive nature and confirmation requirement without any waste.

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?

Given the simple deletion operation, the schema documents all parameters, and annotations cover the safety profile. The description adds permanence and confirmation context. No output schema is needed, and the tool definition is sufficiently complete for an agent to select and invoke correctly.

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 descriptions cover 100% of parameters, including confirm and returnPublicIpInstance. The description's mention of 'confirm=true' mirrors the schema description, adding no new information. Baseline of 3 applies since the schema does the heavy lifting.

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 verb 'delete' and resource 'NAT Gateway instance', with 'Permanently' emphasizing the irreversible nature. This distinguishes it from sibling tools like create_nat_gateway or set_nat_gateway_description.

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 provides clear context for when to use this tool (to permanently remove a NAT Gateway) and the requirement to set confirm=true, but it does not explicitly name alternatives or exclusion conditions. The context is clear enough that no confusion with sibling tools arises.

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

Deploy Server