Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ncloud_create_snapshot

Create a snapshot from a block storage instance to back up data or prepare for recovery. Preview changes with dry run before applying.

Instructions

Create a snapshot from a block storage instance. The source volume is sent to the API as 'originalBlockStorageInstanceNo' — either parameter name is accepted here. Use dryRun=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns a preview without actually creating
regionCodeNoRegion code (e.g. KR, SGN, JPN). Defaults to the client region
snapshotTypeCodeNoSnapshot type — XEN (Gen2, HDD/SSD volumes) ONLY: FULL (default) or INCREMENTAL. INCREMENTAL requires an existing full snapshot of the same volume and is capped at 7 per full snapshot. KVM (Gen3, CB1/CB2/FB1/FB2 volumes) has no snapshot type: the API accepts this parameter on a KVM volume but SILENTLY IGNORES it and creates a FULL snapshot (verified against the live API), so do not rely on it there — omit it for KVM volumes.
blockStorageInstanceNoNoBlock storage instance number to create snapshot from. Sent to the API as originalBlockStorageInstanceNo. Provide this or originalBlockStorageInstanceNo.
blockStorageSnapshotNameNoName for the snapshot (3-30 chars: letters, digits, '-', '_'). Auto-generated when omitted
originalBlockStorageInstanceNoNoSame as blockStorageInstanceNo, spelled with the Ncloud API's own parameter name. Takes precedence when both are given.
blockStorageSnapshotDescriptionNoDescription for the snapshot (max 1000 bytes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv1.11.0
    • changedInput schema / properties / blockStorageInstanceNo / description
      Previous value: -"Block storage instance number to create snapshot from"New value: +"Block storage instance number to create snapshot from. Sent to the API as originalBlockStorageInstanceNo. Provide this or originalBlockStorageInstanceNo."
    • changedInput schema / properties / blockStorageSnapshotDescription / description
      Previous value: -"Description for the snapshot"New value: +"Description for the snapshot (max 1000 bytes)"
    • changedInput schema / properties / blockStorageSnapshotName / description
      Previous value: -"Name for the snapshot"New value: +"Name for the snapshot (3-30 chars: letters, digits, '-', '_'). Auto-generated when omitted"
    • addedInput schema / properties / originalBlockStorageInstanceNo
      Added value: +{
+  "description": "Same as blockStorageInstanceNo, spelled with the Ncloud API's own parameter name. Takes precedence when both are given.",
+  "type": "string"
+}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g. KR, SGN, JPN). Defaults to the client region",
+  "type": "string"
+}
    • addedInput schema / properties / snapshotTypeCode
      Added value: +{
+  "description": "Snapshot type — XEN (Gen2, HDD/SSD volumes) ONLY: FULL (default) or INCREMENTAL. INCREMENTAL requires an existing full snapshot of the same volume and is capped at 7 per full snapshot. KVM (Gen3, CB1/CB2/FB1/FB2 volumes) has no snapshot type: the API accepts this parameter on a KVM volume but SILENTLY IGNORES it and creates a FULL snapshot (verified against the live API), so do not rely on it there — omit it for KVM volumes.",
+  "enum": [
+    "FULL",
+    "INCREMENTAL"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "blockStorageInstanceNo"
-]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations (destructiveHint=false) by explaining the parameter alias behavior and the dryRun preview capability. This helps the agent understand how the tool interacts with the API and what 'preview' mode does. No contradictions with annotations.

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 only three sentences, front-loaded with the core purpose. Every sentence provides necessary information: the action, the alias nuance, and the dryRun preview. No wasted words or redundancy.

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 has a rich schema (100% coverage, detailed param semantics) and an annotation (destructiveHint=false), which lowers the burden on the description. The description is clear about the action and preview capability, but it does not mention return values or response format. Given that there is no output schema, a brief note about the response would improve completeness, but the overall tool definition is minimally 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?

Schema description coverage is 100%, so the baseline is 3. The description repeats the alias information already in the schema (originalBlockStorageInstanceNo) but does not add new semantic meaning beyond what the schema provides. The dryRun mention is also already in the schema. Thus, the description adds no significant value beyond the structured parameter 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 clearly states the action ('Create a snapshot') and identifies the resource ('block storage instance'). It also adds the useful detail about the API parameter name alias, which helps distinguish this tool from other snapshot-related tools like list_snapshots or delete_snapshots.

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?

There is no explicit guidance on when to use this tool vs alternatives, but the dryRun=true hint provides a mild usage suggestion. The tool's name makes its purpose obvious, and the description implies usage through its clarity. However, no exclusions or alternative tool references are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server