ncloud-gov-mcp-server

ncloud_cdss_add_nodes

Add broker nodes to a CDSS cluster by specifying the cluster instance number and the number of nodes (1-10) to scale capacity.

Instructions

Add broker nodes to a CDSS cluster

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>",
      "newBrokerNodeCount": "<newBrokerNodeCount>"
    },
    "name": "ncloud_cdss_add_nodes"
  }
}

Input Schema

Name	Required	Description	Default
`newBrokerNodeCount`	Yes	Number of broker nodes to add (1-10)
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations only include destructiveHint: false, so the description must disclose behavioral traits. It does not mention whether the operation is asynchronous, has side effects, requires permissions, or is reversible. The description only states the action without any context about how it behaves.

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?

The description is one short sentence with no fluff, making it efficient and front-loaded. However, it is under-specified, but that is more a completeness issue than a conciseness issue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this is a mutating operation on a cluster and there is no output schema, the description is incomplete. It does not explain what a CDSS cluster is, any prerequisites, potential impacts, or operation semantics. The agent lacks enough context to use it confidently.

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%, with both parameters (newBrokerNodeCount, serviceGroupInstanceNo) already documented in the input schema. The description adds no additional parameter semantics, so the baseline of 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 states a specific verb ('Add') and resource ('broker nodes to a CDSS cluster'), clearly distinguishing it from sibling tools like ncloud_cdss_change_node_spec (which modifies existing nodes) and ncloud_ses_add_node (for a different service). It is unambiguous about the action being performed.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., cluster must exist), and no exclusions or caveats. It is a bare statement of the action, leaving the agent to infer context.

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

Deploy Server