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

Create a server image from an existing server instance to back up or duplicate its configuration.

Instructions

Create a server image from an existing server 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": {
      "serverInstanceNo": "<serverInstanceNo>"
    },
    "name": "ncloud_create_server_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverImageNameNoName for the new server image
serverInstanceNoYesServer instance number to create image from
serverImageDescriptionNoDescription for the new server image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

The annotations only include destructiveHint=false. The description does not disclose any additional behavioral traits such as permissions required, whether the server is affected, asynchronous nature, or side effects. It adds no context beyond the annotation.

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 with no extraneous information. It clearly conveys the core function in ten words.

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

Completeness3/5

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

For a simple create operation with schema-covered parameters, the description is minimally sufficient. However, there is no output schema and no mention of return values, prerequisites, or potential side effects, and it does not differentiate from similar create-image tools, leaving some contextual gaps.

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 has 100% coverage with descriptions for all three parameters. The description does not add any extra parameter details or clarify relationships, but the schema already documents them, so baseline score is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 resource (server image) from a source (existing server instance). It does not explicitly distinguish from sibling tools like ncloud_create_member_server_image or ncloud_create_server_image_from_snapshot, so it lacks sibling differentiation.

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?

No information about when to use this tool versus alternatives, any prerequisites (e.g., server instance must be stopped or running), or exclusions. The description provides no usage context beyond the basic action.

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