Skip to main content
Glama
Sign In
Docker MCP Server

Docker MCP Server

by good-gis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

docker_remove

Remove a container by its ID or name. Optionally force removal even if it is running.

Instructions

Удалить контейнер

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": {
      "container": "<container>"
    },
    "name": "docker_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoПринудительное удаление (default: false)
containerYesID или имя контейнера

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not reveal that the operation is destructive, what side effects occur (e.g., deleting volumes), or whether a running container can be removed without force. The description only restates the tool's name without any additional behavioral context.

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, direct sentence with zero wasted words. It is fully front-loaded and immediately clear, making it highly concise.

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

Completeness2/5

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

The tool is simple, but the description omits critical context about the destructive nature of the operation, the need to stop a running container, and the purpose of the 'force' flag. With no output schema and minimal description, an agent would lack essential information for safe invocation.

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

Parameters3/5

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

The schema provides full descriptions for both parameters (container and force), achieving 100% coverage. The description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 specifies the verb 'remove' and resource 'container', distinguishing it from sibling tools like docker_run, docker_ps, docker_stop, and docker_logs. No ambiguity about what this tool does.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives. It does not mention that docker_stop might be needed before removal, nor does it explain that the 'force' parameter is relevant for running containers. The description is purely a statement of the action.

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