ncloud-gov-mcp-server

ncloud_ses_add_node

Add data nodes to a Search Engine Service cluster by specifying cluster instance number and node count to scale capacity and performance.

Instructions

Add data nodes to a Search Engine Service 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>",
      "addDataNodeCount": "<addDataNodeCount>"
    },
    "name": "ncloud_ses_add_node"
  }
}

Input Schema

Name	Required	Description	Default
`addDataNodeCount`	Yes	Number of data nodes to add
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description only states the action; it doesn't disclose that this is a scaling operation that may take time, incur costs, or require the cluster to be in a specific state. The annotation provides destructiveHint: false, but the description adds no behavioral context beyond that.

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 a single, front-loaded sentence with no unnecessary words. It directly states the action and target, making it easy to parse and understand.

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?

With no output schema and minimal annotations, the description carries the burden for behavioral disclosure. It lacks prerequisites, operation duration, billing implications, and any constraints or limitations. An agent would need to guess the operational context, making this incomplete for a tool that modifies a cluster.

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?

Both parameters are fully described in the schema (addDataNodeCount as 'Number of data nodes to add' and serviceGroupInstanceNo as 'Cluster instance number'), which covers 100% of parameter semantics. The description doesn't add any additional parameter details, so baseline 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 uses a specific verb and resource ('Add data nodes to a Search Engine Service cluster'), clearly identifying the action and target. It distinguishes itself from sibling tools like ncloud_ses_change_node_spec or ncloud_ses_delete_cluster by focusing on adding data nodes specifically.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that this is for scaling out a cluster, nor does it contrast with changing node specifications or creating a new cluster. An agent has no criteria for selecting this tool over related operations.

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

Deploy Server