Skip to main content
Glama
Sign In
ncloud-mcp-server

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_scheduled_action

DestructiveIdempotent

Delete a scheduled action from an Auto Scaling Group to stop future scaling events. Requires confirm=true to execute the removal.

Instructions

[⚠️ DESTRUCTIVE] Delete a scheduled action from an Auto Scaling Group. Set confirm=true to execute.

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>",
      "scheduledActionName": "<scheduledActionName>"
    },
    "name": "ncloud_delete_scheduled_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
autoScalingGroupNoYesAuto Scaling Group number
scheduledActionNameYesScheduled action name to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already disclose destructiveHint=true and idempotentHint=true. The description adds the critical requirement 'Set confirm=true to execute,' which is also present in the schema's confirm parameter description. While this behavioral detail is important and prominently placed, it is redundant with the schema, so the description adds limited new context beyond structured fields.

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 sentence with a clear warning prefix. It is front-loaded with the destructive nature and states the action and safety requirement concisely. Every phrase is necessary and there is no verbosity.

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 delete operation with 3 parameters, 100% schema coverage, and annotations, the description provides sufficient context. It tells what is deleted, the target resource (Auto Scaling Group), and the confirmation requirement. The lack of output schema is acceptable for a delete tool, and no return value explanation is critical for this kind of operation.

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% for all three parameters, including the confirm requirement. The description does not add any parameter details beyond what the schema already documents, so the baseline of 3 applies.

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 operation: 'Delete a scheduled action from an Auto Scaling Group.' The verb+resource is specific, and the word 'Delete' distinguishes it from sibling tools like ncloud_put_scheduled_action and ncloud_list_scheduled_actions.

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 use case (deleting a scheduled action) but does not explicitly state when to use this tool versus alternatives, nor does it mention related operations like creating or listing scheduled actions. The sibling list provides context, but the description itself contains no usage guidance or exclusions.

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

Deploy Server

Other Tools