Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerImage-removeImage

Destructive

Removes a Docker image from a Dokploy server using its repository, tag, and ID, with an optional force flag to handle images still in use.

Instructions

POST /dockerImage.removeImage

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": {
      "repository": "<repository>",
      "tag": "<tag>",
      "id": "<id>"
    },
    "name": "dockerImage-removeImage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
tagYes
forceNo
serverIdNo
repositoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds only the HTTP method and path, saying nothing about whether removal is permanent, how tag/repository/id combine to select the image, or what the 'force' flag changes — meaningful gaps for a destructive call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here comes from omission rather than editing; the single fragment conveys only a route. There is no front-loaded statement of what the tool actually does to which resource.

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

Completeness1/5

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

For a destructive five-parameter operation with no output schema and no parameter documentation, the definition is wholly inadequate. An agent cannot determine required inputs' meaning or the consequences of calling it from this text.

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

Parameters1/5

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

Schema description coverage is 0% across five parameters, and the description mentions none of them. Critical semantics — the interaction of repository, tag, and id, and the effect of force and serverId — are documented nowhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially the tool name restated as an HTTP route: 'POST /dockerImage.removeImage'. It implies deletion of a Docker image, but adds no scope, target, or differentiation from siblings such as dockerVolume-removeVolume or docker-removeContainer beyond the resource word embedded in the name.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of alternatives, and no preconditions. An agent gets nothing about when removal is appropriate versus inspection via dockerImage-getImages.

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