ncloud-gov-mcp-server

ncloud_cdss_upgrade_status

Check the progress status of a cluster version upgrade operation using the cluster instance number to track completion.

Instructions

Get the progress status of a version upgrade operation

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>"
    },
    "name": "ncloud_cdss_upgrade_status"
  }
}

Input Schema

Name	Required	Description	Default
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral expectations. It only says 'Get', implying a read-only operation, but does not explain what fields are returned, whether an upgrade must be in progress, or how to interpret status values. This is insufficient for an agent to know what to expect from the response.

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 immediately states the purpose. It contains no filler or redundant information, making it easy to scan and process.

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

Completeness3/5

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

The tool is simple (one parameter, no output schema), but the description still leaves gaps: it does not specify what 'progress status' includes (e.g., percentage, current step), whether it can be polled, or what errors might occur if no upgrade is in progress. For a status tool, more detail would be valuable.

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 schema already documents the single parameter (serviceGroupInstanceNo) as 'Cluster instance number', achieving 100% coverage. The description does not add any additional meaning, so the baseline score of 3 applies. It is clear enough but unremarkable.

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 tool retrieves the progress status of a version upgrade operation, using a specific verb ('Get') and resource. This distinguishes it from sibling tools like ncloud_cdss_upgrade_version and ncloud_cdss_upgrade_precheck, which perform the upgrade and precheck respectively.

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

Usage Guidelines3/5

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

The description implies usage after an upgrade has been initiated, but it does not explicitly state when to use this tool versus alternatives like ncloud_cdss_upgrade_version or ncloud_ses_get_upgrade_progress. There is no mention of prerequisites, polling patterns, or when not to use it.

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

Deploy Server