ncloud-gov-mcp-server

ncloud_ses_change_node_spec

Idempotent

Change the server specifications for specific nodes in a Search Engine Service cluster by providing the cluster instance number, node instance numbers, and new product code.

Instructions

Change server specifications for nodes in 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>",
      "computeInstanceNoList": "<computeInstanceNoList>",
      "productCode": "<productCode>"
    },
    "name": "ncloud_ses_change_node_spec"
  }
}

Input Schema

Name	Required	Description
`productCode`	Yes	New server product code
`computeInstanceNoList`	Yes	List of node instance numbers to change
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false, but the description adds no behavioral context beyond what the tool name conveys. It does not disclose whether this is a long-running operation, if nodes are restarted, or if there is any service impact. The description is not contradictory but provides no extra value over the 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 a single, concise sentence that is front-loaded with the action and resource. It contains no filler or redundant information.

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?

Despite a complete schema and useful annotations, the description is too terse for a change operation on a cluster. It does not mention the need for node instance numbers or product codes, nor does it indicate whether the operation is asynchronous or what the outcome/return value looks like. Given no output schema, the description should provide more operational context.

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?

The input schema covers 100% of the three parameters with clear descriptions for each. The description adds no additional meaning beyond what already exists in the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Change server specifications') and the resource ('nodes in a Search Engine Service cluster'). It is specific enough to distinguish from sibling tools like ncloud_ses_change_disk_size or ncloud_ses_change_node_type, though it does not explicitly differentiate 'specifications' from 'type'.

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 such as ncloud_ses_change_node_type or ncloud_ses_change_disk_size. There are no prerequisites mentioned (e.g., retrieving product codes via ncloud_ses_get_node_products) and no exclusions or conditional scenarios.

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

Deploy Server