ncloud-gov-mcp-server

ncloud_delete_server_images

DestructiveIdempotent

Delete server image instances by providing their instance numbers. Confirm the action to permanently remove them.

Instructions

⚠️ Destructive: Delete one or more server image instances. 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": {
      "serverImageInstanceNoList": "<serverImageInstanceNoList>"
    },
    "name": "ncloud_delete_server_images"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`serverImageInstanceNoList`	Yes	List of server image instance numbers to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the warning is redundant but consistent. The description adds the critical gate: the operation will not actually execute unless confirm=true. This is meaningful behavioral context beyond the 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: warning icon, action, and confirmation instruction. Every word carries necessary information with no 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?

With only two parameters, no output schema, and annotations covering destructiveness and idempotency, the description is sufficient for basic invocation. It could mention edge cases like partial failures or dependent resources, but for this simple delete operation, the key behavior (confirm gate) is covered.

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 properties (confirm and serverImageInstanceNoList) documented. The description reinforces the confirm=true rule, but adds no semantic detail beyond what the schema already provides, so the baseline score 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 states 'Delete one or more server image instances' with a clear verb and resource. It doesn't explicitly differentiate from the sibling tool ncloud_delete_member_server_images, so it misses the sibling-distinguishing level, but the core purpose is unambiguous.

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 gives an explicit operational rule: 'Set confirm=true to execute.' It also flags destructive intent. It doesn't mention when-not-to-use or alternatives, but the confirm requirement effectively guides safe invocation.

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

Deploy Server