Skip to main content
Glama
Sign In
opsgate

opsgate

by polymatx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go

docker_restart

Restart a Docker container by name or ID on a configured host. Use it to recover stopped or unhealthy containers while opsgate applies policy checks and audit logging.

Instructions

Restart a Docker container.

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": {
      "container": "<container>"
    },
    "name": "docker_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNotarget host name from the opsgate config; omit for the default host
containerYescontainer name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing beyond the verb. It does not say whether the restart is graceful (SIGTERM then start), whether it causes downtime, what happens if the container is already stopped, or how failures are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single short sentence with the verb and resource front-loaded and zero filler. It is efficient, though arguably terse enough that it is under-specified rather than optimally concise.

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

Completeness3/5

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

For a two-parameter tool with full schema coverage and no output schema, the definition is minimally adequate. However, with no annotations and no mention of restart semantics or failure modes, it leaves gaps an agent would need to guess at.

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%, with both 'container' and the optional 'host' parameter documented (including the opsgate config default). The description adds no meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Restart') and resource ('Docker container'), which cleanly separates it from docker_start, docker_stop, and docker_ps in the sibling set. It does not explicitly contrast itself with those siblings, but the verb alone is unambiguous.

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?

No guidance on when to use this over docker_start/docker_stop or service_restart, and no preconditions stated (e.g., container must exist or be running). The agent must infer usage entirely from the name.

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