ncloud-gov-mcp-server

ncloud_list_scheduled_actions

Read-only

List scheduled actions that have not yet been executed for an Auto Scaling Group to track and manage pending scaling operations.

Instructions

List scheduled actions that have not yet been executed 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_scheduled_actions"
  }
}

Input Schema

Name	Required	Description	Default
`autoScalingGroupNo`	Yes	Auto Scaling Group number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description aligns with that. The description does add the useful scoping detail that only 'not yet been executed' actions are included, but it does not disclose pagination behavior, response format, or behavior when no matching actions exist.

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 one concise sentence of 13 words, front-loaded with the verb 'List' and containing no filler or redundant phrases. Every word 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?

For a simple read-only list operation with one well-documented parameter, the description is mostly adequate. However, since there is no output schema, the return shape, pagination, and ordering of results are not disclosed, leaving a notable gap.

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?

The single parameter autoScalingGroupNo is fully described in the schema ('Auto Scaling Group number') with 100% schema coverage. The description adds no extra meaning beyond the schema, so the baseline score of 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 uses a specific verb ('List') with a clearly identified resource ('scheduled actions') and scope ('that have not yet been executed for an Auto Scaling Group'). This is clear and distinct from sibling tools like ncloud_put_scheduled_action or ncloud_delete_scheduled_action, though it does not explicitly reference those alternatives.

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 vs alternatives, when not to use it, or prerequisites such as how to obtain the required Auto Scaling Group number (e.g., via ncloud_list_asgs). The description only states the basic operation without any contextual direction.

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

Deploy Server