ncloud-gov-mcp-server

ncloud_delete_scaling_policy

DestructiveIdempotent

Delete a scaling policy from an Auto Scaling Group to remove automated scaling rules. Confirm the action to avoid accidental deletion.

Instructions

⚠️ Destructive: Delete a scaling policy 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>",
      "policyName": "<policyName>"
    },
    "name": "ncloud_delete_scaling_policy"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute the destructive operation
`policyName`	Yes	Scaling policy name to delete
`autoScalingGroupNo`	Yes	Auto Scaling Group number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds the critical behavioral detail of the confirm flag requirement, which is not covered by annotations (only destructiveHint and idempotentHint are present). It reinforces the destructive nature already declared by the annotation, providing useful context without contradiction.

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 focused sentence that front-loads the destructive warning and states the purpose and the key execution requirement. There is zero wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (3 simple parameters, no output schema), the description, combined with the annotations and full schema coverage, provides all necessary context for an AI agent to select and invoke the tool correctly. No additional information is missing.

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 three parameters are fully documented in the schema. The description adds no new parameter information beyond echoing the confirm requirement already present in the schema, which meets the baseline but does not go beyond it.

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 (delete) and the target resource (scaling policy from an Auto Scaling Group). It is specific and distinguishes this tool from siblings like ncloud_put_scaling_policy and ncloud_list_scaling_policies.

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

Usage Guidelines4/5

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

The description implies the tool is for deleting scaling policies and explicitly instructs the user to set confirm=true to execute. It does not explicitly name alternatives or exclusion criteria, but for a destructive delete operation, the context is clear and sufficient.

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

Deploy Server