Skip to main content
Glama
Sign In
opsgate

opsgate

by polymatx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go

docker_start

Start a stopped Docker container by name or ID, optionally on a target host from the opsgate config. Omit the host to use the default.

Instructions

Start a stopped 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_start"
  }
}

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?

With no annotations, the description carries the full behavioral burden, yet it only repeats that the container is 'stopped'. It says nothing about behavior on an already-running container, required Docker/host permissions, or side effects of starting.

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 front-loaded sentence with no wasted words. It is efficient, though arguably too terse to carry the guidance a mutation-class tool needs.

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?

The tool is simple (two params, one required), so the description is close to sufficient. But with no annotations and no output schema, it should still say what happens on an already-running container and confirm the operation's effect.

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 coverage is 100%, so 'container' and 'host' are fully documented in the schema, including the host-default behavior. The description adds no meaning beyond that, making the baseline 3 appropriate.

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 (Start) and resource (stopped Docker container), so the action is unambiguous. It does not, however, distinguish itself from siblings like docker_restart or docker_stop, which an agent must infer from the names alone.

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 use this versus docker_restart, or that the container must already exist and be stopped. No prerequisites, no exclusions, no named alternative.

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