infrastructure-mcp

Overview Schema Source Related Servers Discussions Admin

docker_restart

Restart a Docker container on a host, requiring confirm:true; set dry_run:true to preview the exact command without acting.

Instructions

Restart a container on a Docker host. This is a dangerous, service-impacting action: it requires confirm: true, and returns without acting if confirmation is missing. Set dry_run: true to see the exact command that would run without needing confirm at all.

Input Schema

TableJSON Schema

Name	Required	Description
`server`	Yes	the inventory server name to check
`confirm`	No	must be true to actually restart the container; otherwise the tool reports what it would do without acting
`dry_run`	No	if true, report the exact command that would be run and return without acting or requiring confirm
`container`	Yes	container name or ID to restart

Output Schema

TableJSON Schema

Name	Required	Description	Default
`server`	Yes
`status`	Yes
`message`	Yes
`container`	Yes
`timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.1Oct 15, 2026

addedInput schema / properties / dry_run

Added value: +{
+  "description": "if true, report the exact command that would be run and return without acting or requiring confirm",
+  "type": "boolean"
+}

First observedv0.1.0Oct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it flags the action as dangerous and service-impacting, explains the confirm gate and the no-op behavior when confirmation is missing, and clarifies that dry_run bypasses confirm. It omits permission/auth requirements and any cautions about container state loss, so it is not exhaustive.

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?

Two sentences, front-loaded with the core action before the danger warning and the dry_run escape hatch. Every clause carries behavioral information; nothing is padding.

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?

An output schema exists, so return values need not be explained, and the description covers the operation's safety contract and confirmation semantics adequately. The only gap is the absence of any note on required permissions or the blast radius of restarting a container.

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?

Schema description coverage is 100%, so the schema already documents server, container, confirm and dry_run. The description restates confirm and dry_run semantics in prose without adding format or syntax detail beyond the schema, making this the baseline case.

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?

States a specific verb and resource ('Restart a container on a Docker host'), which cleanly distinguishes it from read-only siblings like docker_ps, docker_logs and docker_stats. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Explicitly states the precondition for acting ('requires confirm: true') and offers a safe alternative path ('Set dry_run: true to see the exact command... without needing confirm at all'). It does not name a sibling tool to use instead when a restart is the wrong choice, so it falls short of the 5-level routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.