ncloud-gov-mcp-server

ncloud_delete_snapshots

DestructiveIdempotent

Permanently delete block storage snapshots. Set confirm=true to execute this destructive operation.

Instructions

⚠️ Destructive: Permanently delete one or more block storage snapshot 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": {
      "blockStorageSnapshotInstanceNoList": "<blockStorageSnapshotInstanceNoList>"
    },
    "name": "ncloud_delete_snapshots"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already mark destructiveHint and idempotentHint. The description adds that deletion is permanent and requires confirm=true to execute, providing a safety interlock beyond the boolean destructive hint. It also alerts with '⚠️ Destructive,' adding useful context about irreversibility.

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 sentence that efficiently conveys the destructive warning, the resource being operated on, and the execution requirement. It is front-loaded with the warning and contains no unnecessary words.

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 2-parameter destructive tool with good schema coverage and idempotent/destructive annotations, the description covers the core behavior and safety mechanism. It could mention what happens when confirm=false, but that is implied by the schema default and the explicit 'Set confirm=true to execute.' Overall it is sufficiently complete.

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?

Both parameters are fully described in the schema (confirm and blockStorageSnapshotInstanceNoList) with meaningful descriptions. The tool description adds no extra parameter semantics beyond what the schema already provides, so the baseline score 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 tool permanently deletes one or more block storage snapshot instances. The verb 'delete' and specific resource 'block storage snapshot instances' distinguish it from sibling deletion tools like ncloud_delete_block_storage or ncloud_delete_nas_snapshot.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as listing snapshots first to obtain instance numbers. The only usage-related instruction is 'Set confirm=true to execute,' which concerns parameter behavior rather than tool selection context.

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

Deploy Server