Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_cache_manual_backup

Creates a manual backup for a Cloud Cache instance, enabling point-in-time data protection and recovery. Use the returned backup name to view details.

Instructions

Create a manual backup for a Cloud DB for Cache instance. The backup file name is assigned by the server — read it back with ncloud_list_cache_manual_backup_details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionCodeNoRegion code (e.g., KR, JPN, SGN)
cloudCacheInstanceNoYesCloud Cache instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • removedInput schema / properties / cloudCacheManualBackupName
      Removed value: -{
-  "description": "Manual backup name",
-  "type": "string"
-}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheInstanceNo",
-  "cloudCacheManualBackupName"
-]New value: +[
+  "cloudCacheInstanceNo"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

It discloses a useful behavioral fact: the backup file name is assigned by the server and must be read back via a separate call. However, with only destructiveHint=false in annotations, the description does not cover other important behavior like asynchronous execution, cost implications, or what the response contains. The added context is meaningful but not rich.

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 terse sentences with no filler. The main action is front-loaded and the follow-up instruction earns its place by preventing confusion about how to obtain the backup file name.

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 two-parameter create operation with no output schema, the description provides the necessary invocation target and a follow-up retrieval path. It could have mentioned whether the backup is created asynchronously or whether a region default applies, but the existing guidance is sufficient for correct invocation.

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?

The input schema already covers both parameters with descriptions (100% coverage). The tool description adds no parameter-level detail beyond the schema, 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 uses a specific verb-resource pair: 'Create a manual backup for a Cloud DB for Cache instance.' It clearly stands apart from sibling cache tools like ncloud_list_cache_manual_backups, ncloud_delete_cache_manual_backup, and ncloud_export_cache_backup.

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 makes its use case evident through the 'manual backup' phrasing and routes the agent to ncloud_list_cache_manual_backup_details for retrieving the server-assigned backup name. It does not explicitly mention exclusions, such as when to prefer scheduled/automatic backups or export operations, but the context is clear enough.

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