Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-startContainer

Idempotent

Start a Docker container by its container ID, optionally targeting a specific server ID, to resume a stopped container in Dokploy.

Instructions

POST /docker.startContainer

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo
containerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the agent knows the call is idempotent and touches an external system. The description adds nothing on top: it does not say what happens if the container is already running, whether it errors on a missing container, what permissions are required, or what the response contains. For a mutating lifecycle operation with no destructiveHint/readOnlyHint coverage, that is a significant gap.

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 short but not concise in the useful sense: it is an under-specified route stub with no front-loaded statement of purpose or behavior. Brevity here reflects missing content rather than disciplined editing.

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?

With no output schema, 0% schema description coverage, and only two hints in annotations, the description should explain the operation's effect and failure modes. It explains nothing, so an agent cannot call this correctly beyond guessing from the name.

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% with two parameters, so the description carries the full burden of explaining containerId (required, pattern-constrained) and serverId (optional). It provides no meaning for either, leaving the agent to guess at how serverId affects routing.

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?

"POST /docker.startContainer" only restates the tool name and its HTTP verb; it adds no verb+resource phrasing beyond what the identifier already conveys. An agent learns nothing about scope, e.g. whether it starts a container on a specific server or what a 'start' entails versus a restart.

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

Usage Guidelines1/5

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

There is no when-to-use guidance at all, and no distinction from closely related siblings such as docker-restartContainer, docker-stopContainer, or docker-killContainer. The agent must infer selection purely from the tool 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