Skip to main content
Glama
Sign In
docker-mcp-server

docker-mcp-server

by L337-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

container_restart

Restart a container in one call: stop it, wait up to stop_timeout_seconds, then start it again. Returns the full container inspect payload for verification.

Instructions

Restart a container: stop then start again in one call.

The container receives its configured stop signal (STOPSIGNAL, default SIGTERM), SIGKILL after stop_timeout_seconds, and is then started. Use container_stop/container_start to do the halves separately. When the server runs containerized it refuses to restart its own container.

Args: stop_timeout_seconds: Seconds between the stop signal and SIGKILL

Returns: dict: The container's full inspect payload after the restart

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": {
      "id_or_name": "<id_or_name>"
    },
    "name": "container_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_nameYes
stop_timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by detailing the STOPSIGNAL behavior, default SIGTERM, SIGKILL after stop_timeout_seconds, the subsequent start, and the self-container refusal. These are meaningful behavioral details not present in readOnlyHint or destructiveHint.

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 front-loaded with the core action, then groups behavioral details, the alternative tool, the caveat, and a compact Args/Returns block. Every sentence contributes distinct, useful information with no filler.

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

Completeness4/5

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

For a two-parameter restart operation with no output schema, the description provides the return type, the key timing behavior, and the self-restart limitation. It is only slightly incomplete because the required identifier parameter is not explained and container preconditions are not mentioned.

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 description gives precise meaning for stop_timeout_seconds: seconds between the stop signal and SIGKILL, which is valuable because schema description coverage is 0%. However, the required id_or_name parameter is not described in the Args section, leaving the agent to infer that it takes a container ID or name from the property name and tool context.

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 first sentence defines the verb and resource precisely: restart a container by stopping then starting it in one call. It also distinguishes the tool from container_stop/container_start, making its combined behavior clear.

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

Usage Guidelines5/5

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

It explicitly directs the agent to use container_stop/container_start when the halves are needed separately. It also flags the important caveat that a containerized server refuses to restart its own container, which is essential for correct tool selection.

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