Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-removeContainer

Destructive

Removes a Docker container by its container ID, with an optional server ID to target a specific Docker server.

Instructions

POST /docker.removeContainer

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": {
      "containerId": "<containerId>"
    },
    "name": "docker-removeContainer"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
containerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/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, yet the description contributes nothing beyond them. It says nothing about whether the container must be stopped first, whether data/volumes are destroyed, irreversibility, or permissions required.

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?

The text is short but that is under-specification rather than conciseness; a bare URL path is not useful front-loaded information for an agent. There is nothing to trim because almost nothing is said.

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 two-parameter mutation tool with no output schema and no parameter documentation, the definition is essentially empty. An agent cannot confidently determine preconditions, targeting semantics, or consequences before invoking it.

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 two parameters, so the description carries the full burden and delivers nothing. It does not clarify that containerId identifies the target container or what serverId selects (e.g., a remote Docker host), leaving both parameters semantically opaque.

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 only the HTTP route 'POST /docker.removeContainer', which essentially restates the tool name rather than stating in prose what the tool does. An agent can guess removal from the name, but the definition adds no verb-plus-resource explanation and does not distinguish it from siblings such as docker-killContainer or docker-stopContainer.

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, when-not-to-use, or alternative guidance whatsoever. The removal-vs-stop-vs-kill decision, arguably the most important routing choice among these siblings, is left entirely to inference from the name.

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