Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-stopContainer

Idempotent

Stops a running Docker container on a Dokploy server by container ID and optional server ID, helping halt workloads or apply updates.

Instructions

POST /docker.stopContainer

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

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 supply openWorldHint and idempotentHint, so the lower bar applies, yet the description adds nothing beyond the route: it does not say whether the container is terminated gracefully, whether it persists afterward, what happens if it is already stopped, or what is returned. No contradiction with annotations, but zero added 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.

Conciseness2/5

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

It is short with no wasted sentences, but that shortness is under-specification rather than concision: a bare route string is not a usable front-loaded summary.

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 lifecycle-mutating tool with two undocumented parameters and no output schema, the definition leaves an agent without enough information to call it correctly or predict its effect. Nothing beyond the endpoint path is conveyed.

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 (serverId and containerId), and the description supplies no meaning for either. The containerId pattern and the role of serverId (which daemon/host to target) are completely undocumented.

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 only restates the HTTP route 'POST /docker.stopContainer', which is a tautology of the tool name. An agent can infer 'stop a container' from the name alone, but the description contributes no verb+resource statement of its own and does nothing to separate it from docker-killContainer, docker-removeContainer or docker-restartContainer.

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 prerequisites, and no mention of the closely related siblings (kill, restart, remove). With four nearby tools that all affect container lifecycle, the absence of any routing cue is a real gap.

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