ncloud-gov-mcp-server

ncloud_delete_cache_manual_backup

DestructiveIdempotent

Permanently delete a Cloud Cache manual backup. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a Cloud Cache manual backup. 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": {
      "cloudCacheManualBackupNo": "<cloudCacheManualBackupNo>"
    },
    "name": "ncloud_delete_cache_manual_backup"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`cloudCacheManualBackupNo`	Yes	Cloud Cache manual backup number 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 and idempotentHint=true. The description adds crucial context that deletion is permanent and irreversible, and requires an explicit confirm=true flag to execute, which enhances the annotation-provided safety profile without contradiction.

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 concise sentences with an immediate warning and clear action. No filler words; every sentence adds value, making it highly efficient.

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 destructive tool with full schema coverage and appropriate annotations, the description is largely sufficient. It covers the core purpose, safety requirements, and parameters, though it could optionally note idempotency behavior for non-existent backups.

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 description coverage is 100%, so the schema already fully documents both parameters. The description repeats the confirm requirement, adding no additional meaning beyond what the schema states.

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 clearly identifies the resource ('Cloud Cache manual backup'), adding 'permanently' to convey the irreversible nature. It distinguishes from sibling tools like list/create manual backup by explicitly stating the delete action.

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 does not explicitly name alternatives or state when versus when not to use the tool. However, the confirm=true instruction is a usage prerequisite for executing the destructive operation, though it doesn't cover selection criteria among sibling tools.

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

Deploy Server