ncloud-gov-mcp-server

ncloud_create_cache_manual_backup

Create a manual backup for a Cloud DB for Cache instance by specifying the instance number and desired backup name.

Instructions

Create a manual backup for a Cloud DB for Cache instance

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": {
      "cloudCacheInstanceNo": "<cloudCacheInstanceNo>",
      "cloudCacheManualBackupName": "<cloudCacheManualBackupName>"
    },
    "name": "ncloud_create_cache_manual_backup"
  }
}

Input Schema

Name	Required	Description	Default
`cloudCacheInstanceNo`	Yes	Cloud Cache instance number
`cloudCacheManualBackupName`	Yes	Manual backup name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotation destructiveHint=false already discloses that this operation is not destructive, so the description doesn't need to repeat that. However, the description adds no extra behavioral context, such as whether the backup is asynchronous, if the instance must be in a certain state, or if there are storage implications.

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 is clearly front-loaded with the essential information. Every word earns its place, with no extraneous content.

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?

The tool is simple (2 required params, no output schema, low complexity) and the schema/annotations already cover parameters and destructive behavior. The description is sufficient for the tool's purpose, though it could mention whether the operation is synchronous or returns a job ID, but that is not mandatory given the simplicity.

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 coverage is 100%, with each parameter having a brief description. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 action ('Create') and the specific resource ('manual backup for a Cloud DB for Cache instance'), which distinguishes it from sibling tools like list_cache_manual_backups and delete_cache_manual_backup. It is concise and unambiguous.

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 implies usage (create a manual backup) but does not explicitly state when to use it versus alternatives, such as automatic backups or when a manual backup is appropriate. There are no exclusions or alternative tool mentions.

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

Deploy Server