Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_cache_manual_backup

DestructiveIdempotent

Permanently deletes selected Cloud Cache manual backup files for a given instance; requires file names from backup details and confirm=true to execute.

Instructions

⚠️ Destructive: Permanently delete one or more Cloud Cache manual backup files. Backups are identified by instance number plus file name (from ncloud_list_cache_manual_backup_details), not by a backup ID. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
regionCodeNoRegion code (e.g., KR, JPN, SGN)
fileNameListYesBackup file names to delete (e.g. ['20220315', '20220322']) — from ncloud_list_cache_manual_backup_details
cloudCacheInstanceNoYesCloud Cache instance number the backups belong to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • addedInput schema / properties / cloudCacheInstanceNo
      Added value: +{
+  "description": "Cloud Cache instance number the backups belong to",
+  "type": "string"
+}
    • removedInput schema / properties / cloudCacheManualBackupNo
      Removed value: -{
-  "description": "Cloud Cache manual backup number to delete",
-  "type": "string"
-}
    • addedInput schema / properties / fileNameList
      Added value: +{
+  "description": "Backup file names to delete (e.g. ['20220315', '20220322']) — from ncloud_list_cache_manual_backup_details",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheManualBackupNo"
-]New value: +[
+  "cloudCacheInstanceNo",
+  "fileNameList"
+]
  2. First observedv1.10.1

TDQS

A4.4/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: the confirm=true requirement for execution and the identification method (instance + filename, not backup ID). This goes beyond the annotations by explaining the confirmation guardrail and how to target backups correctly. No 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?

Three sentences with a clear warning prefix, then the action, identification method, and execution requirement. Every sentence earns its place, and the destructive warning is front-loaded for safety.

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 destructive operation with a confirmation flag, the description covers what, how, and the guardrail. It does not describe the response format or whether the operation is synchronous, but given no output schema and the presence of idempotentHint, this is a minor gap. The reference to the listing tool for inputs is sufficient for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already cover all parameters (100% coverage). The description adds meaning by stating that fileNameList values come from ncloud_list_cache_manual_backup_details and that confirm must be true to execute. This explains the operational semantics beyond the schema's field descriptions.

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 states a specific verb (delete) and resource (Cloud Cache manual backup files), and clarifies the identification method (instance number plus file name, not backup ID). This clearly distinguishes it from sibling tools like ncloud_delete_cache_instance.

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?

It implies usage for manual backup deletion and explicitly references the sibling tool ncloud_list_cache_manual_backup_details for obtaining file names, which gives the agent a clear source for inputs. However, it does not explicitly state when not to use this tool versus other deletion tools, though context makes it obvious.

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

Deploy Server

Other Tools