Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_server_images

DestructiveIdempotent

Delete server images by providing their image numbers. Requires confirm=true to execute; destructive operation for server images only.

Instructions

⚠️ Destructive: Delete one or more server images (serverImageNo from ncloud_get_server_images). For user-created member images use ncloud_delete_member_server_images. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
serverImageNoListYesList of server image numbers to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • removedInput schema / properties / serverImageInstanceNoList
      Removed value: -{
-  "description": "List of server image instance numbers to delete",
-  "items": {
-    "type": "string"
-  },
-  "minItems": 1,
-  "type": "array"
-}
    • addedInput schema / properties / serverImageNoList
      Added value: +{
+  "description": "List of server image numbers to delete",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "serverImageInstanceNoList"
-]New value: +[
+  "serverImageNoList"
+]
  2. First observedv1.10.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description reinforces it with a warning glyph and, more valuably, discloses that the call is gated behind confirm=true rather than executing on submission. It does not say what cascade effects deletion has on servers using the image or whether the delete is reversible.

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?

Three short, front-loaded clauses: warning and action first, routing second, execution gate last. No filler sentences and nothing buried.

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?

For a two-parameter destructive tool with full schema coverage, an output schema is unnecessary, and the annotations plus description together cover safety, scope, routing, and the confirm gate. An agent has everything needed to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning by identifying where serverImageNo values come from (ncloud_get_server_images) and by framing confirm as the execution switch. The confirm flag is already described in the schema, so the added value is modest rather than decisive.

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?

States a specific verb and resource ('Delete one or more server images'), names the batch scope, and explicitly distinguishes itself from the near-identical sibling ncloud_delete_member_server_images. An agent can route between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives the selection condition against the alternative ('For user-created member images use ncloud_delete_member_server_images'), points to the source of the required IDs (ncloud_get_server_images), and states the execution gate (confirm=true). All three usage-relevant facts are present.

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