ncloud-gov-mcp-server

ncloud_ncr_delete_image

DestructiveIdempotent

Permanently deletes a container image from a given registry, removing all associated tags. Requires explicit confirmation to execute.

Instructions

⚠️ Destructive: Permanently delete a container image from a registry. All associated tags will be removed. 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": {
      "registryName": "<registryName>",
      "imageName": "<imageName>"
    },
    "name": "ncloud_ncr_delete_image"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute the destructive operation
`imageName`	Yes	Name of the image to delete
`registryName`	Yes	Name of the registry

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotation destructiveHint already flags destructiveness, but the description adds valuable behavioral context: the operation is permanent and removes all associated tags. This goes beyond the raw annotation and clarifies exactly what will be destroyed.

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, information-dense sentence with a warning emoji, followed by a short instruction. Every word earns its place—no fluff, front-loaded with the destructive warning.

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 simple destructive delete tool, the description covers the operation, prerequisites (confirm), and consequences (tags removed). Annotations cover idempotency and destructiveness; the schema covers parameters. No output schema is needed, and the description is sufficient for an agent to select and 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 meaning by explaining the effect of deleting the image (all tags removed), which is not in the schema. It also reiterates confirm=true, which is already in the schema, but the overall effect enriches the imageName semantics.

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: 'Permanently delete a container image from a registry' with the specific effect 'All associated tags will be removed.' This distinguishes it from sibling tools like ncloud_ncr_delete_tag (which deletes a single tag) and ncloud_ncr_delete_registry (which deletes a registry).

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 provides clear usage context: it is destructive, permanent, and requires confirm=true to execute. However, it does not explicitly state when not to use it or mention alternatives (e.g., delete_tag instead of delete_image if only a tag should be removed).

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

Deploy Server