Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_upgrade_version

Upgrade a cluster's Search Engine version by completing the required snapshot and precheck steps first, ensuring a valid upgrade path.

Instructions

Upgrade the Search Engine version of a cluster. Run ncloud_ses_precheck_upgrade first. ⚠️ The pre-check requires an existing snapshot — it fails with 10154 if the cluster has none, so the full chain is ncloud_ses_set_snapshot_api_key → ncloud_ses_get_snapshot_buckets → ncloud_ses_create_snapshot → ncloud_ses_precheck_upgrade → this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoYesRegion number (from ncloud_get_regions — this is regionNo, not the region code)
targetVersionCodeYesTarget version code (from ncloud_ses_get_versions)
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • addedInput schema / properties / regionNo
      Added value: +{
+  "description": "Region number (from ncloud_get_regions — this is regionNo, not the region code)",
+  "type": "number"
+}
    • removedInput schema / properties / searchEngineVersionCode
      Removed value: -{
-  "description": "Target version code",
-  "type": "string"
-}
    • addedInput schema / properties / targetVersionCode
      Added value: +{
+  "description": "Target version code (from ncloud_ses_get_versions)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "searchEngineVersionCode"
-]New value: +[
+  "regionNo",
+  "serviceGroupInstanceNo",
+  "targetVersionCode"
+]
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are empty, so the description carries the behavioral disclosure burden. It does this well by revealing the snapshot requirement, the 10154 failure mode, and the complete prerequisite chain. It stops short of full transparency because it does not mention async/long-running behavior or the likely follow-up ncloud_ses_get_upgrade_progress, but it goes well beyond a minimal mutation description.

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?

Three sentences and every sentence earns its place: the core action, the mandatory pre-check, and the exact chain with the failure condition. The warning is front-loaded and the chain is compact, making the required workflow easy to follow.

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?

For a cluster upgrade tool with three documented parameters, no annotations, and no output schema, the description is highly complete: it encodes the prerequisite chain, error condition, and parameter sources. It loses a point because it does not indicate what happens after invocation, such as checking upgrade progress with ncloud_ses_get_upgrade_progress, which would make the full lifecycle explicit.

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 each parameter already annotated with its provenance, e.g., 'from ncloud_get_regions' and 'from ncloud_ses_get_versions.' The tool description adds no further parameter-level detail beyond the schema, 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 begins with a specific verb and resource: 'Upgrade the Search Engine version of a cluster.' It is immediately clear what operation is performed, and the prerequisite chain references ncloud_ses_precheck_upgrade, distinguishing this tool as the final upgrade step rather than the pre-check.

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

Usage Guidelines5/5

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

The description explicitly says 'Run ncloud_ses_precheck_upgrade first' and then provides the full ordered chain ending in this tool. It also gives the conditional rule: the pre-check fails with 10154 if no snapshot exists, so the agent knows exactly when each prerequisite is needed.

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