ncloud-gov-mcp-server

ncloud_suspend_processes

Idempotent

Suspend specific scaling processes on an Auto Scaling Group to prevent automated scaling actions. Temporarily pause processes like health checks or alarms during maintenance or troubleshooting.

Instructions

Suspend specific 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_suspend_processes"
  }
}

Input Schema

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

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?

The description does not add behavioral detail beyond the idempotentHint and destructiveHint annotations. It does not explain that suspension only affects future scaling activities, whether it is reversible, or that it does not modify existing instances. This leaves important context unstated for a state-changing operation.

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?

One sentence, front-loaded with the action and object. No filler or redundancy.

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 description is adequate for a simple 2-parameter tool, but it omits how to discover valid scaling process codes (suggested by sibling ncloud_get_scaling_process_types) and the operational impact of suspension. Annotations and schema cover safety and parameters, but the description lacks these contextual pointers.

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 documentation covers both parameters (autoScalingGroupNo and scalingProcessCodeList) with clear descriptions, so the baseline is met. The tool description adds no additional parameter semantics, such as allowed process codes or the relationship to ncloud_get_scaling_process_types.

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 uses a specific verb ('Suspend') and resource ('scaling processes') and clearly identifies the target ('Auto Scaling Group'). It distinguishes from sibling tools like ncloud_resume_processes and other ASG operations.

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 the tool is used to suspend processes on an ASG but provides no explicit guidance on when to use it versus alternatives such as ncloud_resume_processes or setting desired capacity. There are no exclusions or prerequisites mentioned.

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

Deploy Server