Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_server_image_from_snapshot

Create a server image from block storage snapshots by providing the original server image number and a list of snapshot instances.

Instructions

Create a server image from block storage snapshots

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": {
      "originalServerImageNo": "<originalServerImageNo>",
      "blockStorageSnapshotInstanceNoList": "<blockStorageSnapshotInstanceNoList>"
    },
    "name": "ncloud_create_server_image_from_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverImageNameNoName for the new server image
originalServerImageNoYesOriginal server image number
serverImageDescriptionNoDescription for the new server image
blockStorageSnapshotInstanceNoListYesList of block storage snapshot instance numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations include destructiveHint=false, so the agent knows this is not a destructive operation. The description adds no further behavioral context (e.g., whether the operation is asynchronous, effects on the snapshots, or required states). Since annotations already cover the safety profile, the description is adequate but not enriching.

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, concise sentence ('Create a server image from block storage snapshots') that is front-loaded with the action and resource. It contains no redundant words or irrelevant details.

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 create operation with no output schema, the description adequately covers the action and source. The schema fully documents parameters. The description lacks details about prerequisites or asynchronous behavior, but is sufficient for a straightforward image creation tool given the available annotations and schema.

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 schema provides 100% description coverage for all parameters, so the description does not need to explain basic parameter meaning. It adds the contextual hint that the source is block storage snapshots, but it does not elaborate on relationships between originalServerImageNo and blockStorageSnapshotInstanceNoList. Baseline of 3 is appropriate given the high schema coverage.

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 the specific verb 'Create' and identifies the resource 'server image' with the source 'block storage snapshots', which clearly differentiates it from sibling image-creation tools like ncloud_create_server_image and ncloud_create_member_server_image.

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 states the specific use case (creating a server image from block storage snapshots), which implicitly guides the agent to select this tool when working with snapshots. However, it does not explicitly name alternative tools or provide exclusionary guidance, so it falls short of a 5.

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