Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_cache_instance

Create a Redis/Valkey cache instance from a config group. Preview with dryRun before provisioning.

Instructions

Create a new Cloud DB for Cache (Redis/Valkey) instance. Requires a config group — create one with ncloud_create_cache_config_group or pick an existing configGroupNo from ncloud_list_cache_config_groups. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isHaNoHigh availability (default: false)
vpcNoYesVPC number
dryRunNoIf true, returns a preview without actually creating the instance
isBackupNoEnable backup (default: false)
subnetNoYesPrivate subnet number to create the instance in
backupTimeNoBackup time in HH:mm format (e.g. '01:15'). Required when isBackup=true and isAutomaticBackup=false
regionCodeNoRegion code (e.g., KR, JPN, SGN)
shardCountNoMaster node count, CLUSTER mode only (3-10, default: 3)
configGroupNoYesConfig group number (from ncloud_list_cache_config_groups or ncloud_create_cache_config_group)
cloudCachePortNoCache TCP port. Default: 6379; a custom port must be in 10000-20000
generationCodeNoServer generation: G2 | G3
shardCopyCountNoReplica count per shard, CLUSTER mode only (0-4, default: 0)
engineVersionCodeNoCache engine version code. Default: latest
isAutomaticBackupNoLet the server pick the backup time (default: true). If false, backupTime is required
cloudCacheDbmsCodeNoDBMS type: Redis (default) | Valkey
cloudCacheModeCodeYesCache mode: SIMPLE (standalone) | CLUSTER. Must match the config group version suffix (-simple / -cluster)
cloudCacheProductCodeNoCache server spec code. Default: minimum spec
cloudCacheServiceNameYesCache service name (3-15 chars: letters, numbers, Korean, hyphen)
backupFileRetentionPeriodNoBackup retention period in days (1-7, default: 1)
cloudCacheImageProductCodeNoCache image product code. Default: auto-selected
cloudCacheServerNamePrefixYesServer name prefix (3-15 chars: lowercase letters, numbers, hyphen)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changedv1.15.0
    • changedInput schema / properties / backupFileRetentionPeriod / description
      Previous value: -"Backup retention period in days (1-30)"New value: +"Backup retention period in days (1-7, default: 1)"
    • addedInput schema / properties / backupFileRetentionPeriod / maximum
      Added value: +7
    • addedInput schema / properties / backupFileRetentionPeriod / minimum
      Added value: +1
    • changedInput schema / properties / backupTime / description
      Previous value: -"Backup time (HH:mm format)"New value: +"Backup time in HH:mm format (e.g. '01:15'). Required when isBackup=true and isAutomaticBackup=false"
    • removedInput schema / properties / cloudCacheConfigGroupNo
      Removed value: -{
-  "description": "Config group number to apply",
-  "type": "string"
-}
    • addedInput schema / properties / cloudCacheDbmsCode
      Added value: +{
+  "description": "DBMS type: Redis (default) | Valkey",
+  "enum": [
+    "Redis",
+    "Valkey"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / cloudCacheImageProductCode / description
      Previous value: -"Cache image product code (Redis/Valkey version)"New value: +"Cache image product code. Default: auto-selected"
    • addedInput schema / properties / cloudCacheModeCode
      Added value: +{
+  "description": "Cache mode: SIMPLE (standalone) | CLUSTER. Must match the config group version suffix (-simple / -cluster)",
+  "enum": [
+    "SIMPLE",
+    "CLUSTER"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / cloudCachePort / description
      Previous value: -"Cache port number (default: 6379)"New value: +"Cache TCP port. Default: 6379; a custom port must be in 10000-20000"
    • changedInput schema / properties / cloudCacheProductCode / description
      Previous value: -"Cache server product (spec) code"New value: +"Cache server spec code. Default: minimum spec"
    • changedInput schema / properties / cloudCacheServerNamePrefix / description
      Previous value: -"Server name prefix"New value: +"Server name prefix (3-15 chars: lowercase letters, numbers, hyphen)"
    • addedInput schema / properties / cloudCacheServerNamePrefix / maxLength
      Added value: +15
    • changedInput schema / properties / cloudCacheServiceName / description
      Previous value: -"Cache service name (3-20 chars, lowercase letters and numbers)"New value: +"Cache service name (3-15 chars: letters, numbers, Korean, hyphen)"
    • addedInput schema / properties / cloudCacheServiceName / maxLength
      Added value: +15
    • addedInput schema / properties / configGroupNo
      Added value: +{
+  "description": "Config group number (from ncloud_list_cache_config_groups or ncloud_create_cache_config_group)",
+  "type": "string"
+}
    • addedInput schema / properties / engineVersionCode
      Added value: +{
+  "description": "Cache engine version code. Default: latest",
+  "type": "string"
+}
    • addedInput schema / properties / generationCode
      Added value: +{
+  "description": "Server generation: G2 | G3",
+  "enum": [
+    "G2",
+    "G3"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / isAutomaticBackup
      Added value: +{
+  "description": "Let the server pick the backup time (default: true). If false, backupTime is required",
+  "type": "boolean"
+}
    • removedInput schema / properties / isAutomaticFailover
      Removed value: -{
-  "description": "Whether to enable automatic failover",
-  "type": "boolean"
-}
    • changedInput schema / properties / isBackup / description
      Previous value: -"Whether to enable automatic backup"New value: +"Enable backup (default: false)"
    • addedInput schema / properties / isHa
      Added value: +{
+  "description": "High availability (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
    • changedInput schema / properties / shardCopyCount / description
      Previous value: -"Number of replicas per shard"New value: +"Replica count per shard, CLUSTER mode only (0-4, default: 0)"
    • addedInput schema / properties / shardCopyCount / maximum
      Added value: +4
    • addedInput schema / properties / shardCopyCount / minimum
      Added value: +0
    • changedInput schema / properties / shardCount / description
      Previous value: -"Number of shards (for cluster mode)"New value: +"Master node count, CLUSTER mode only (3-10, default: 3)"
    • addedInput schema / properties / shardCount / maximum
      Added value: +10
    • addedInput schema / properties / shardCount / minimum
      Added value: +3
    • changedInput schema / properties / subnetNo / description
      Previous value: -"Subnet number"New value: +"Private subnet number to create the instance in"
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheServiceName",
-  "vpcNo",
-  "subnetNo"
-]New value: +[
+  "cloudCacheServiceName",
+  "cloudCacheServerNamePrefix",
+  "vpcNo",
+  "subnetNo",
+  "configGroupNo",
+  "cloudCacheModeCode"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

Annotations only include destructiveHint: false, so the description carries the burden of behavioral disclosure. It does add the dryRun behavior (preview without creating) and the requirement for a config group, which are useful. However, it does not disclose other potential behaviors such as provisioning time, asynchronous completion, or cost implications. This is a partial disclosure but not comprehensive.

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 three sentences, front-loaded with the core purpose. Each sentence adds distinct value: purpose, prerequisite/alternatives, and a safety tip (dryRun). No fluff or redundant information. It is appropriately concise for a tool with a rich schema.

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?

Given the tool's complexity (21 params, 6 required) and the very descriptive schema, the description covers the essential non-obvious guidance: the config group prerequisite and dryRun. It does not need to repeat schema details. While it could mention provisioning duration or async behavior, that's not explicitly known, and the schema already handles parameter semantics. Overall, it's sufficient for an agent to use the tool correctly.

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 21 parameters, so the baseline is 3. The description adds minimal extra meaning beyond highlighting the config group dependency and dryRun, both of which are already in the schema. It does not explain any parameters beyond what the schema provides, so it adds little value over the structured data.

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 states a specific verb and resource: 'Create a new Cloud DB for Cache (Redis/Valkey) instance.' This clearly distinguishes it from other create tools (e.g., create_mysql_instance) and aligns with the tool name. It also names the prerequisite config group, further clarifying its role in the cache ecosystem.

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 explicitly instructs the user to first create a config group via ncloud_create_cache_config_group or select an existing one via ncloud_list_cache_config_groups, providing clear alternative paths. It also mentions dryRun for previewing. However, it doesn't explicitly state when NOT to use this tool versus other instance creation tools, though the cache-specific naming makes that largely implicit.

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