ncloud-gov-mcp-server

ncloud_ses_create_snapshot

Create a snapshot of a Search Engine Service cluster and store it in an Object Storage bucket for backup or migration. Specify the cluster instance number and bucket name to proceed.

Instructions

Create a snapshot of a Search Engine Service cluster

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>",
      "bucketName": "<bucketName>"
    },
    "name": "ncloud_ses_create_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`bucketName`	Yes	Object Storage bucket name for snapshot storage
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With only destructiveHint: false in annotations, the description carries the burden of disclosing behavioral traits. It merely states 'create a snapshot' without explaining whether the operation is asynchronous, what side effects occur, whether the bucket must already exist, or what the response/result will be. This is a significant gap for a mutation tool.

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 clear sentence that conveys the essential purpose with no unnecessary words. It is concise and well-structured, stating the action and the target resource directly.

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

Completeness2/5

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

The description lacks important contextual details for an agent to use the tool correctly: it doesn't specify prerequisites, expected outcomes, or how this manual snapshot creation fits with related snapshot features (e.g., scheduled snapshots). The absence of an output schema makes the lack of return-value information more impactful.

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%: bucketName is described as 'Object Storage bucket name for snapshot storage' and serviceGroupInstanceNo as 'Cluster instance number'. The tool description adds no additional parameter meaning beyond the schema, so the baseline score 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 resource (a snapshot of a Search Engine Service cluster), using a specific verb and resource that distinguishes it from sibling tools like ncloud_ses_get_snapshot_history or ncloud_ses_set_snapshot_schedule. The scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as whether it is for manual snapshots as opposed to scheduled snapshots, or if any prerequisites (e.g., existing bucket or cluster state) are required. No alternative tools are mentioned.

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

Deploy Server