Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-killContainer

Idempotent

Terminate a running Docker container in Dokploy by specifying its container ID, optionally targeting a server, to stop the container process.

Instructions

POST /docker.killContainer

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-killContainer"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
containerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds no behavioral context beyond the bare POST verb that hints at mutation. It omits whether the process is forcibly terminated, what happens to unsaved state, and whether the container is removed afterward — important gaps for a destructive operation with no destructiveHint declared.

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 the brevity is under-specification rather than conciseness: a single route string with no verb, object, or context. There is nothing to front-load because no useful content exists.

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 container-terminating mutation with a required identifier, an optional server selector, and no output schema, the description is wholly inadequate. An agent cannot determine the semantics, side effects, or parameter usage from 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% for two parameters, and the description supplies no meaning for either. It never explains that containerId is required or what serverId selects (presumably the Docker host), leaving the agent entirely dependent on bare field names.

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.killContainer', which restates the tool name rather than describing the action. It never says what killing a container means (SIGKILL? graceful stop? forced?) or how it differs from siblings like docker-stopContainer or docker-removeContainer.

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?

There is no when-to-use guidance: nothing distinguishes kill from stop, restart, or remove. The reader must infer the choice entirely from the tool name, with no exclusions or preconditions stated.

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