Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_cache_config_group

Create a Cloud Cache config group on Naver Cloud Platform by specifying a name and engine version/mode. Use dryRun to preview changes before applying them.

Instructions

Create a new Cloud Cache config group. cloudCacheVersion combines engine version and mode (e.g. '8.1.6-simple' = Standalone, '7.2.11-cluster' = Cluster) — list valid values with ncloud_list_cache_config_group_versions. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns a preview without actually creating the config group
regionCodeNoRegion code (e.g., KR, JPN, SGN)
configGroupNameYesConfig group name (3-15 chars: lowercase letters, numbers, hyphen; must start with a letter and end with a letter or number)
cloudCacheVersionYesEngine version + mode, e.g. '8.1.6-simple' | '7.2.11-cluster' (use ncloud_list_cache_config_group_versions)
cloudCacheDbmsCodeNoDBMS type: Redis (default) | Valkey
configGroupDescriptionNoConfig group description (max 255 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.15.0
    • removedInput schema / properties / cloudCacheConfigGroupName
      Removed value: -{
-  "description": "Config group name",
-  "type": "string"
-}
    • addedInput schema / properties / cloudCacheDbmsCode
      Added value: +{
+  "description": "DBMS type: Redis (default) | Valkey",
+  "enum": [
+    "Redis",
+    "Valkey"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / cloudCacheImageProductCode
      Removed value: -{
-  "description": "Cache image product code for the config group",
-  "type": "string"
-}
    • addedInput schema / properties / cloudCacheVersion
      Added value: +{
+  "description": "Engine version + mode, e.g. '8.1.6-simple' | '7.2.11-cluster' (use ncloud_list_cache_config_group_versions)",
+  "type": "string"
+}
    • addedInput schema / properties / configGroupDescription
      Added value: +{
+  "description": "Config group description (max 255 chars)",
+  "maxLength": 255,
+  "type": "string"
+}
    • addedInput schema / properties / configGroupName
      Added value: +{
+  "description": "Config group name (3-15 chars: lowercase letters, numbers, hyphen; must start with a letter and end with a letter or number)",
+  "maxLength": 15,
+  "type": "string"
+}
    • removedInput schema / properties / description
      Removed value: -{
-  "description": "Config group description",
-  "type": "string"
-}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheConfigGroupName",
-  "cloudCacheImageProductCode"
-]New value: +[
+  "configGroupName",
+  "cloudCacheVersion"
+]
  2. First observedv1.10.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only carry destructiveHint: false, so the description carries most of the behavioral disclosure burden. It adds genuinely useful context beyond annotations: the dryRun preview capability ('Use dryRun=true to preview without creating') and the semantic mapping of version formats to modes (Standalone/Cluster). It does not disclose return value or async behavior, but the non-destructive annotation is consistent with a create operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose, then the tricky composite parameter, then the safety valve. Each sentence earns its place. Minor redundancy: the version-format examples partially duplicate the schema description for cloudCacheVersion, but the added mode-to-name mapping justifies the overlap.

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 6-parameter create tool with no output schema, the description covers the essentials: purpose, the most error-prone parameter with format guidance, and the dryRun preview option. It does not describe the return value or mention prerequisites/async operation status, but the sibling list includes ncloud_get_operation_status, and the selection/invocation knowledge an agent needs is largely present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, setting the baseline at 3. The description adds value beyond the schema by explaining what the version-mode combinations actually mean ('8.1.6-simple' = Standalone, '7.2.11-cluster' = Cluster) and clarifying dryRun's preview semantics. This supplements the schema's terse examples rather than merely repeating them.

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?

States a specific verb and resource ('Create a new Cloud Cache config group') that clearly distinguishes it from sibling creation tools like ncloud_create_cache_instance and from the list/delete config-group siblings. The purpose is unambiguous and immediately understandable.

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?

Provides clear operational context by naming the exact sibling to consult for valid parameter values ('list valid values with ncloud_list_cache_config_group_versions'). However, it does not explicitly state when NOT to use this tool or contrast it with ncloud_create_cache_instance, so exclusion guidance is missing.

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