ncloud-gov-mcp-server

ncloud_ses_create_cluster_g3

Creates a Search Engine Service (SES) G3 cluster on Naver Cloud Gov with manager, master, and data nodes. Use dryRun to preview configuration before provisioning.

Instructions

Create a new Search Engine Service cluster (G3/KVM). 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": {
      "clusterName": "<clusterName>",
      "searchEngineVersionCode": "<searchEngineVersionCode>",
      "searchEngineDashboardPort": "<searchEngineDashboardPort>",
      "searchEngineUserName": "<searchEngineUserName>",
      "searchEngineUserPassword": "<searchEngineUserPassword>",
      "softwareProductCode": "<softwareProductCode>",
      "vpcNo": "<vpcNo>",
      "managerNodeSubnetNo": "<managerNodeSubnetNo>",
      "managerNodeServerSpecCode": "<managerNodeServerSpecCode>",
      "dataNodeSubnetNo": "<dataNodeSubnetNo>",
      "dataNodeCount": "<dataNodeCount>",
      "dataNodeServerSpecCode": "<dataNodeServerSpecCode>",
      "dataNodeStorageSize": "<dataNodeStorageSize>",
      "loginKeyName": "<loginKeyName>"
    },
    "name": "ncloud_ses_create_cluster_g3"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	Yes	VPC number
`dryRun`	No	If true, preview only without creating
`clusterName`	Yes	Cluster name (3-15 chars, lowercase+numbers+'-')
`loginKeyName`	Yes	Authentication key name
`dataNodeCount`	Yes	Number of data nodes (3-10)
`isDualManager`	No	Manager node redundancy (default: true)
`masterNodeCount`	No	Number of master nodes (3 or 5)
`dataNodeSubnetNo`	Yes	Data node subnet number
`masterNodeSubnetNo`	No	Master node subnet
`dataNodeStorageSize`	Yes	Data node storage size in GB (100-2000)
`managerNodeSubnetNo`	Yes	Manager node subnet number
`softwareProductCode`	Yes	OS type code (from getClusterServerImageList)
`searchEngineUserName`	Yes	Admin account ID (3-15 chars)
`dataNodeServerSpecCode`	Yes	Data node server spec code
`searchEngineVersionCode`	Yes	Search engine version code
`masterNodeServerSpecCode`	No	Master node server spec code
`searchEngineUserPassword`	Yes	Admin password (8-20 chars)
`isMasterOnlyNodeActivated`	No	Enable dedicated master nodes
`managerNodeServerSpecCode`	Yes	Manager node server spec code (from getServerSpecList)
`searchEngineDashboardPort`	Yes	Dashboard port (1025-65534, not 9090/9200/9300)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description adds the dryRun preview behavior, which is beyond the minimal annotation (destructiveHint=false). However, it does not disclose other behavioral traits such as provisioning time, asynchronous execution, or response format. The sparse annotation means the description carries some but not full burden.

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 concise sentences, with the primary action front-loaded and the dryRun tip in a separate sentence. Every word earns its place with no wasted content.

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 20-parameter cluster creation tool with no output schema, this description is minimal. The schema is richly described, but the description lacks guidance on prerequisites, how to obtain codes, or what to expect after invocation. It is adequate but has clear 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-specific details beyond the schema; the only mention of dryRun repeats the schema description, providing no additional value.

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 'Search Engine Service cluster' while adding the qualifier 'G3/KVM' to distinguish it from the generic ncloud_ses_create_cluster sibling. This clearly states what the tool does and differentiates it from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'Use dryRun=true to preview' as a usage hint, but it does not explicitly state when to use this tool over ncloud_ses_create_cluster or other cluster management tools. The G3/KVM qualifier implies a specific use case but does not name alternatives or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server