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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_nas_volume

Create a new NAS volume in a specified VPC and zone with NFS or CIFS protocol, size, encryption, and access control. Use dryRun to preview before actual creation.

Instructions

Create a new NAS volume instance. Use dryRun=true to preview.

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": {
      "volumeName": "<volumeName>",
      "volumeSize": "<volumeSize>",
      "volumeAllotmentProtocolTypeCode": "<volumeAllotmentProtocolTypeCode>",
      "vpcNo": "<vpcNo>",
      "zoneCode": "<zoneCode>"
    },
    "name": "ncloud_create_nas_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcNoYesVPC number where the NAS volume will be created
dryRunNoIf true, returns a preview without actually creating
zoneCodeYesZone code (e.g. KR-1, KR-2)
volumeNameYesNAS volume name (3~20 characters, alphanumeric)
volumeSizeYesVolume size in GB (500~10000, in 100GB increments)
cifsUserNameNoCIFS user name (required when protocol is CIFS)
cifsUserPasswordNoCIFS user password (required when protocol is CIFS)
isEncryptedVolumeNoWhether to encrypt the volume
isReturnProtectionNoWhether to enable return protection
nasVolumeDescriptionNoNAS volume description
serverInstanceNoListNoList of server instance numbers for access control
volumeAllotmentProtocolTypeCodeYesVolume protocol type code (NFS or CIFS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations only state destructiveHint=false. The description adds the behavioral nuance that dryRun=true returns a preview without actually creating, which is useful context beyond the schema and annotations. However, it does not disclose other behavioral traits such as asynchronous execution, cost implications, or permission requirements.

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 two short sentences with no filler. The first sentence front-loads the action, and the second provides a distinct usage tip, making every word earn its place.

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 complex create tool with 12 parameters, no output schema, and minimal annotations, the description is quite sparse. The schema covers parameter semantics, but the description omits return value expectations, prerequisites, or operational considerations beyond dryRun. It is adequate but leaves gaps for such a complex operation.

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% parameter coverage with detailed descriptions for all 12 parameters, so the description doesn't need to add parameter meaning. Mentioning dryRun is redundant with the schema's description, and no other param semantics are provided. Baseline 3 applies.

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 names the resource 'new NAS volume instance', clearly distinguishing it from sibling tools that list, get, change, or delete NAS volumes. It also signals the alternative dryRun mode, reinforcing that this is the creation entry point.

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 provides a clear usage tip: 'Use dryRun=true to preview', which tells the agent when to use the dryRun flag. It does not explicitly compare with alternatives like create_nas_snapshot or list_nas_volumes, but the verb and resource name imply the creation context.

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