ncloud-mcp-server

ncloud_put_scaling_policy

Create or update an Auto Scaling Group scaling policy to define adjustment type, scaling amount, and cooldown period.

Instructions

Create or update a scaling policy 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>",
      "policyName": "<policyName>",
      "adjustmentTypeCode": "<adjustmentTypeCode>",
      "scalingAdjustment": "<scalingAdjustment>"
    },
    "name": "ncloud_put_scaling_policy"
  }
}

Input Schema

Name	Required	Description
`cooldown`	No	Cooldown period in seconds after scaling
`policyName`	Yes	Scaling policy name
`minAdjustmentStep`	No	Minimum adjustment step for percentage-based scaling
`scalingAdjustment`	Yes	Scaling adjustment value
`adjustmentTypeCode`	Yes	Adjustment type (CHANG — exact change, PRCNT — percentage, EXACT — set to exact number)
`autoScalingGroupNo`	Yes	Auto Scaling Group number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations are empty, so the description carries the full burden of disclosing behavioral traits. It only says 'Create or update' without explaining side effects, idempotency, permission requirements, error conditions, or impact on existing policies. This is insufficient for a mutating 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?

The description is a single sentence with no wasted words. It efficiently conveys the core action and resource. Every word earns its place, making it highly concise and well-structured.

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?

With no output schema and empty annotations, the description must provide more context. It lacks information about when to use the tool, behavior on existing policies, prerequisites, or how adjustment types affect outcomes. The minimal description leaves significant gaps for an agent trying to invoke it correctly.

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 of the 6 parameters having a description. The tool description adds no additional parameter semantics, but it does not need to since the schema is comprehensive. This aligns with the baseline of 3.

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 action ('Create or update') and the resource ('a scaling policy for an Auto Scaling Group'), which is specific and distinguishes it from related sibling tools that list, delete, or execute scaling policies. The verb+resource combination is unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or references to sibling tools such as ncloud_list_scaling_policies or ncloud_delete_scaling_policy. The description simply states what it does without contextualizing usage.

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

Deploy Server