Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_add_node

Scale out a Search Engine Service cluster by adding data nodes. Provide the cluster instance number and the number of additional nodes to increase capacity.

Instructions

Add data nodes to a Search Engine Service cluster. ⚠️ newDataNodeCount is HOW MANY TO ADD, not the resulting total — a cluster with 3 data nodes given newDataNodeCount=4 ends up with 7. ⚠️ Node count cannot be reduced afterwards: SES has no scale-down operation, so the only way back from adding too many is deleting the cluster.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newDataNodeCountYesHow many data nodes to ADD. This is a delta, not the resulting total
serviceGroupInstanceNoYesCluster instance number (path segment)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • removedInput schema / properties / addDataNodeCount
      Removed value: -{
-  "description": "Number of data nodes to add",
-  "type": "number"
-}
    • addedInput schema / properties / newDataNodeCount
      Added value: +{
+  "description": "How many data nodes to ADD. This is a delta, not the resulting total",
+  "minimum": 1,
+  "type": "number"
+}
    • changedInput schema / properties / serviceGroupInstanceNo / description
      Previous value: -"Cluster instance number"New value: +"Cluster instance number (path segment)"
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "addDataNodeCount"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "newDataNodeCount"
+]
  2. First observedv1.10.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint=false annotation, the description discloses the operation's irreversible nature, the fact that SES has no scale-down operation, and that recovery requires deleting the entire cluster. This is high-value behavioral context that an agent cannot infer from the schema or annotations.

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 compact and front-loaded with the core action, followed by two essential warnings. Every sentence earns its place, and the warning formatting makes the critical delta semantics and irreversibility impossible to miss.

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

Completeness5/5

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

For a simple two-parameter mutation tool, the description covers what the tool does, how the parameter should be interpreted, and the most important operational consequence (irreversibility). No output schema is present, but an agent has everything needed to select and invoke the tool correctly.

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?

The schema already covers both parameters at 100%, including the delta meaning of newDataNodeCount. The description reinforces this with a concrete example (3 + 4 = 7), which adds useful illustrative meaning beyond the schema's plain statement.

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 and resource: 'Add data nodes to a Search Engine Service cluster.' It clearly distinguishes this from sibling operations like creating, deleting, or restarting a cluster, and the 'data nodes' qualifier separates it from Kafka-related node operations.

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?

The description gives clear context by explaining that newDataNodeCount is a delta and that node count cannot later be reduced, which helps an agent decide when this tool is appropriate. It does not explicitly name alternative tools or state when-not-to-use conditions beyond the irreversibility warning, so it falls just short of a 5.

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