Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-restartContainer

Idempotent

Restart a Docker container by container ID on a chosen Dokploy server to recover a stopped or unhealthy service.

Instructions

POST /docker.restartContainer

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

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 idempotentHint=true and openWorldHint=true, so the safety profile is partly carried by structured fields, but the description adds nothing beyond them. It does not say whether the container is restarted gracefully or forcibly, whether state is preserved, or what the caller gets back; the endpoint string conveys only that HTTP POST is used.

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 brief, but brevity here reflects under-specification rather than conciseness: a single route string with no front-loaded statement of purpose. Nothing is wasted because nothing meaningful 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 mutating container operation with two parameters at 0% schema coverage, no output schema, and only partial annotations, the description should explain effect and parameters. It explains neither, so an agent must guess at semantics such as what serverId does and how restart differs from start/stop.

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 both parameters, so the description is the only place meaning could be supplied, and it supplies none. containerId and serverId (including whether serverId selects a remote Docker host) are left entirely unexplained, and the required containerId pattern is documented nowhere in prose.

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 "POST /docker.restartContainer", which restates the tool name and its transport rather than stating what the tool does. A reader can infer a container is restarted from the name alone, but the description contributes no verb, scope, or effect of its own, and it does not distinguish restart from the nearby docker-startContainer, docker-stopContainer, or docker-killContainer siblings.

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 guidance on when to restart versus stop/start or kill a container, no mention of prerequisites, and no indication of what happens to in-flight processes. The only implicit cue is the tool's own name, which is not guidance supplied by the description.

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