ncloud-mcp-server

ncloud_list_scaling_policies

Read-only

List all scaling policies for a specified Auto Scaling Group. Supply the group number to retrieve policy details that govern scaling actions.

Instructions

List all scaling policies 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>"
    },
    "name": "ncloud_list_scaling_policies"
  }
}

Input Schema

Name	Required	Description
`pageNo`	No	Page number for pagination
`pageSize`	No	Page size for pagination
`autoScalingGroupNo`	Yes	Auto Scaling Group number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read operation, so the description does not need to repeat that. It adds the 'all' scope and ASG-specific targeting, but does not mention pagination behavior, return format, or potential empty results. This is adequate baseline transparency.

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?

A single, front-loaded sentence with no filler. Every word is essential and the description earns its place.

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 minimal but adequate for a straightforward list operation. However, the claim of 'all' conflicts slightly with pagination parameters without explaining whether it auto-paginates, and the lack of an output schema means the return value is not described. It meets the minimum bar but does not exceed it.

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%, so all parameters (pageNo, pageSize, autoScalingGroupNo) are already documented. The description does not add any additional meaning beyond the schema, such as how pagination interacts with the claim of 'all'.

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 verb ('List'), the resource ('scaling policies'), and the scope ('for an Auto Scaling Group'), distinguishing it from other policy-listing tools like ncloud_gtm_list_policies or ncloud_list_policies. The singular required parameter autoScalingGroupNo reinforces the intended target.

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 explicit guidance is given about when to use this tool over alternatives, such as ncloud_put_scaling_policy or ncloud_delete_scaling_policy. The context is implied by the name and description but lacks any stated exclusions or prerequisites.

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

Deploy Server