ncloud-gov-mcp-server

ncloud_resume_processes

Idempotent

Resume previously suspended scaling processes for an Auto Scaling Group to restore automatic scaling.

Instructions

Resume previously suspended scaling processes for an Auto Scaling Group

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": {
      "autoScalingGroupNo": "<autoScalingGroupNo>",
      "scalingProcessCodeList": "<scalingProcessCodeList>"
    },
    "name": "ncloud_resume_processes"
  }
}

Input Schema

Name	Required	Description	Default
`autoScalingGroupNo`	Yes	Auto Scaling Group number
`scalingProcessCodeList`	Yes	List of scaling process codes to resume

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/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 description's addition of 'previously suspended' provides some context about the target state. However, it does not disclose behavior if called on non-suspended processes, potential asynchronous side effects, or what response to expect.

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 with no unnecessary words. It is front-loaded with the verb and resource, making it easy to parse.

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 simple two-parameter mutation with idempotent and non-destructive annotations, the description is adequately complete. It covers the operation scope, and the schema provides full parameter descriptions. No output schema exists, but given the tool's simplicity, the lack of return-value details is acceptable.

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%: both autoScalingGroupNo and scalingProcessCodeList have descriptions. The tool description does not add meaning beyond the schema; it does not clarify what scaling process codes are valid, though sibling tool ncloud_get_scaling_process_types exists for that purpose.

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 ('Resume') and the resource ('scaling processes for an Auto Scaling Group'), and the phrase 'previously suspended' clarifies the targeted state. It is distinct from sibling tools like ncloud_suspend_processes and ncloud_get_scaling_process_types, though it does not explicitly name alternatives.

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 processes have been suspended, but it does not explicitly state when to use this tool versus alternatives like ncloud_suspend_processes, nor does it mention any prerequisites or exclusions. The guidance is mostly implied by the verb 'resume'.

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

Deploy Server