Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_change_node_spec

Idempotent

Change node specifications in a Search Engine Service cluster by specifying new server type codes for master, manager, or data nodes. Update only the roles you need.

Instructions

Change server specifications per node role in a Search Engine Service cluster. Send only the roles you are changing — read the changeable specs with ncloud_ses_get_node_product_for_change (G2) or ncloud_ses_get_node_spec_for_change_g3 (G3) first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNodeProductCodeNoNew data node server type code
masterNodeProductCodeNoNew master node server type code
managerNodeProductCodeNoNew manager node server type code
serviceGroupInstanceNoYesCluster instance number (path segment)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.0
    • removedInput schema / properties / computeInstanceNoList
      Removed value: -{
-  "description": "List of node instance numbers to change",
-  "items": {
-    "type": "number"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / dataNodeProductCode
      Added value: +{
+  "description": "New data node server type code",
+  "type": "string"
+}
    • addedInput schema / properties / managerNodeProductCode
      Added value: +{
+  "description": "New manager node server type code",
+  "type": "string"
+}
    • addedInput schema / properties / masterNodeProductCode
      Added value: +{
+  "description": "New master node server type code",
+  "type": "string"
+}
    • removedInput schema / properties / productCode
      Removed value: -{
-  "description": "New server product code",
-  "type": "string"
-}
    • changedInput schema / properties / serviceGroupInstanceNo / description
      Previous value: -"Cluster instance number"New value: +"Cluster instance number (path segment)"
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "computeInstanceNoList",
-  "productCode"
-]New value: +[
+  "serviceGroupInstanceNo"
+]
  2. First observedv1.10.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds the behavioral rule to send only changed rolesainer but does not disclose potential side effects like downtime or cost implications. It does not contradict the annotations, and the added prerequisite context is useful but limited.

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 sentences with no waste. The primary action is stated first, followed by a critical usage rule and prerequisite references. Every sentence earns its place.

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

Completeness4/5

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

The tool has a required parameter and three optional parameters, and the description covers the key prerequisite of reading changeable specs. It lacks explicit mention of the serviceGroupInstanceNo parameter, but the schema documents that. Without an output schema, it need not describe return values at length. Overall, sufficient for an agent to call 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?

Schema description coverage is 100%, but the description adds key semantic value beyond the schema: it instructs that only the roles being changed should be sent, implying that omitted product codes remain unchanged. This clarifies the optional nature of the three node product code parameters in a way the schema alone does not.

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 verb 'Change' and the resource 'server specifications per node role in a Search Engine Service cluster,' making it distinct from sibling tools like ncloud_ses_change_node_type. It also emphasizes 'Send only the roles you are changing,' which precisely defines the operation's scope.

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 explicit guidance on how to use the tool: 'Send only the roles you are changing' and 'read the changeable specs with ... first.' It names the prerequisite read methods. However, it does not explicitly state when not to use this tool versus alternatives, such as changing node type with ncloud_ses_change_node_type.

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