mcpdockery

by Chandrakant1988

Overview Schema Source Related Servers Discussions Admin

delete_image

Delete a Docker image by tag or ID, with forced removal even if referenced by stopped containers. Preview the deletion first, then confirm to permanently remove it.

Instructions

Delete a Docker image by tag or ID. Removed even if still referenced by a stopped container (force). Destructive and irreversible. The first call (confirm=False, the default) does NOT delete anything — it only previews what would happen. Only pass confirm=True after the user has explicitly agreed to the deletion. Args: image_name: image name to be deleted confirm: must be True to actually perform the deletion (default False)

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": {
      "image_name": "<image_name>"
    },
    "name": "delete_image"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`image_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries full responsibility and does well by stating the operation is destructive, irreversible, and that the default confirm=False performs no deletion. This clearly sets expectations about side effects.

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 compact and well-structured, using short paragraphs and bullet-like Args entries. Every sentence adds necessary information about behavior or parameters, with no fluff.

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?

It covers the destructive nature, the preview mode, and the explicit confirmation requirement, which is the critical context for this tool. The presence of an output schema mitigates the lack of return-value details, so the description is sufficiently complete.

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?

The Args section explains image_name as the image to be deleted and confirm as the flag that must be True to perform deletion, defaulting to False. This adds meaningful semantics beyond the bare schema, though image_name format is not detailed.

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 tool deletes a Docker image by tag or ID, and highlights the force behavior with stopped containers. This distinguishes it from sibling tools like delete_container and list_images.

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?

It explicitly explains the two-phase confirm flow: confirm=False previews, confirm=True actually deletes, and only after explicit user agreement. It does not compare against alternative tools, but it gives clear operational guidance for safe usage.

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