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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_create_cluster

Create a new CDSS Kafka cluster in Naver Cloud Gov. Use dryRun to preview configuration before provisioning.

Instructions

Create a new CDSS (Kafka) cluster (G2). 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>",
      "kafkaVersionCode": "<kafkaVersionCode>",
      "configGroupNo": "<configGroupNo>",
      "kafkaManagerUserName": "<kafkaManagerUserName>",
      "kafkaManagerUserPassword": "<kafkaManagerUserPassword>",
      "softwareProductCode": "<softwareProductCode>",
      "vpcNo": "<vpcNo>",
      "managerNodeSubnetNo": "<managerNodeSubnetNo>",
      "managerNodeProductCode": "<managerNodeProductCode>",
      "brokerNodeSubnetNo": "<brokerNodeSubnetNo>",
      "brokerNodeCount": "<brokerNodeCount>",
      "brokerNodeProductCode": "<brokerNodeProductCode>",
      "brokerNodeStorageSize": "<brokerNodeStorageSize>"
    },
    "name": "ncloud_cdss_create_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcNoYesVPC number
dryRunNoPreview without creating
clusterNameYesCluster name (3-15 chars, lowercase+numbers+'-')
configGroupNoYesConfig group number
brokerNodeCountYesNumber of broker nodes (3-10)
kafkaVersionCodeYesKafka version code (from get_kafka_versions)
brokerNodeSubnetNoYesBroker node subnet number
managerNodeSubnetNoYesManager node subnet number
softwareProductCodeYesOS type code (from get_os_products)
kafkaManagerUserNameYesCMAK access account ID
brokerNodeProductCodeYesBroker node server type code
brokerNodeStorageSizeYesBroker storage in GB (100-2000, 10GB increment)
managerNodeProductCodeYesManager node server type code
kafkaManagerUserPasswordYesCMAK access account password

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, and the description does not contradict that. It adds the dryRun preview behavior, but for a create operation that provisions cloud resources, it does not mention side effects like persistent resource creation, potential costs, or asynchronous execution. The description goes slightly beyond annotations but lacks deeper behavioral context.

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, front-loaded with the core purpose and containing a useful tip. There is no fluff, and every word contributes to the tool's understanding.

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?

Given the complexity (14 parameters, no output schema, minimal annotations), the description is somewhat under-specified. It does not mention prerequisites, expected response, or that related lookup tools should be consulted first. However, the rich schema descriptions partially compensate, and the core purpose is clear.

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 parameters are fully documented in the schema. The description only reinforces the dryRun parameter and does not add additional semantic meaning. This matches the baseline for full schema coverage.

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 clearly states the action (Create), the specific resource (new CDSS (Kafka) cluster), and the generation (G2), which distinguishes it from other cluster creation tools like ncloud_ses_create_cluster and ncloud_nks_create_cluster. The dryRun tip additionally signals a validation mode, further clarifying scope.

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 implies when to use this tool (when provisioning a new CDSS Kafka cluster) and includes a practical tip about using dryRun=true to preview. However, it does not mention prerequisites such as needing a VPC, subnets, or looking up version/product codes via sibling tools like ncloud_cdss_get_kafka_versions, nor does it explicitly exclude alternatives.

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