ncloud-gov-mcp-server

ncloud_ses_precheck_upgrade

Verify cluster readiness for upgrading to a specific search engine version. Run a pre-check to identify potential issues before applying the upgrade.

Instructions

Pre-check before upgrading Search Engine version

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

Input Schema

Name	Required	Description	Default
`serviceGroupInstanceNo`	Yes	Cluster instance number
`searchEngineVersionCode`	Yes	Target version code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are present, so the description carries full behavioral disclosure. It merely states 'Pre-check' without indicating whether it is read-only, what it validates, or what the response looks like. This leaves the agent unable to infer side effects or safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is one short sentence ('Pre-check before upgrading Search Engine version') with no waste. However, it is quite terse and lacks any additional context that could be added without hurting conciseness.

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?

Without an output schema, the description should explain what the precheck reports (e.g., compatibility issues), but it only gives a generic phrase. It also omits any details about prerequisites or the upgrade workflow, leaving the context incomplete for a mutation-adjacent operation.

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?

Both parameters are fully described in the schema (100% coverage) with 'Cluster instance number' and 'Target version code'. The description adds no additional parameter semantics, but the schema already covers the meaning, so baseline 3 applies.

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 a pre-check before Search Engine version upgrade, using 'Pre-check' as the verb and 'upgrading Search Engine version' as the resource. It distinguishes from actual upgrade and progress tracking tools in the sibling list, though it does not elaborate on the specific checks performed.

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 phrase 'before upgrading' implies the tool is a prerequisite to ncloud_ses_upgrade_version, but no explicit guidance or alternatives are listed. It conveys the timing but not when to invoke it versus other tools.

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

Deploy Server