Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_export_cache_backup

Read-only

Export a Cloud Cache backup file to an Object Storage bucket for archival or recovery. Specify the backup file and target bucket to complete the transfer.

Instructions

Export one Cloud Cache backup file to an Object Storage bucket. Get fileName from ncloud_list_cache_backup_details (SYSTEM) or ncloud_list_cache_manual_backup_details (MANUAL), and the bucket from ncloud_list_cache_buckets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNameYesBackup file name to export (e.g. '20210315')
bucketNameYesDestination Object Storage bucket name
regionCodeNoRegion code (e.g., KR, JPN, SGN)
backupTypeModeYesWhich backup family the file belongs to: SYSTEM | MANUAL
cloudCacheInstanceNoYesCloud Cache instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.15.0
    • addedInput schema / properties / backupTypeMode
      Added value: +{
+  "description": "Which backup family the file belongs to: SYSTEM | MANUAL",
+  "enum": [
+    "SYSTEM",
+    "MANUAL"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / bucketName / description
      Previous value: -"Object Storage bucket name"New value: +"Destination Object Storage bucket name"
    • removedInput schema / properties / cloudCacheExportObjectList
      Removed value: -{
-  "description": "List of full object names to export",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / cloudCacheServerInstanceNo
      Removed value: -{
-  "description": "Cloud Cache server instance number",
-  "type": "string"
-}
    • addedInput schema / properties / fileName
      Added value: +{
+  "description": "Backup file name to export (e.g. '20210315')",
+  "type": "string"
+}
    • removedInput schema / properties / folderPath
      Removed value: -{
-  "description": "Folder path in the bucket",
-  "type": "string"
-}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheInstanceNo",
-  "cloudCacheServerInstanceNo",
-  "bucketName",
-  "cloudCacheExportObjectList"
-]New value: +[
+  "cloudCacheInstanceNo",
+  "fileName",
+  "backupTypeMode",
+  "bucketName"
+]
  2. First observedv1.10.1

TDQS

A3.7/5.0
Behavior1/5

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

Annotation Contradiction: annotations declare readOnlyHint=true, but the description describes exporting/copying a backup file into an Object Storage bucket, which is an externally visible write operation. No context is given about bucket write permissions, overwrite behavior, or whether the export runs asynchronously, making the safety profile actively misleading.

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?

Two sentences with no filler: the action is stated first, then the non-obvious parameter dependencies are given. Every sentence adds useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description makes invocation feasible by covering the action and the sources for the two non-obvious parameters. However, it omits behavioral context such as side effects, required permissions, and whether the operation is synchronous, and the readOnlyHint contradiction further weakens the completeness of the operational picture.

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 coverage is 100%, so parameters are already documented. The description adds meaningful sourcing semantics by linking backupTypeMode to specific list APIs and directing the agent to ncloud_list_cache_buckets for the bucket name, which helps the agent populate the required fields correctly.

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 first sentence states a concrete action (export one Cloud Cache backup file) with a clear source resource and destination (Object Storage bucket). This distinguishes it from the many sibling backup-export tools for MySQL, PostgreSQL, MongoDB, and MSSQL, as well as from list-only cache tools.

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 explicitly instructs the agent where to obtain fileName (ncloud_list_cache_backup_details for SYSTEM, ncloud_list_cache_manual_backup_details for MANUAL) and bucketName (ncloud_list_cache_buckets). It does not list exclusion conditions, but the main ambiguity is value sourcing, which is resolved clearly.

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