Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getContainers

Read-onlyIdempotent

Retrieves Docker containers from a specified Dokploy server, helping you inspect running services and manage deployment infrastructure.

Instructions

GET /docker.getContainers

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docker-getContainers"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safe-read profile is known without the text. The description contributes nothing beyond that: no mention of pagination, whether stopped containers are included, result volume, or how remote-server fan-out (openWorld) manifests. No contradiction, but no added behavior either.

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?

Extremely short, but the brevity is under-specification rather than economy: the single line is a route restatement that earns no place in the definition. There is no front-loaded statement of what the tool returns or scopes.

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

Completeness2/5

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

With no output schema and a 0%-covered input schema, the description carries the full burden and discharges none of it. For a container-listing tool in a crowded family where a serverId scoping decision must be made, an agent has to guess at both inputs and results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter, serverId, is never mentioned in the description. The parameter is a discriminating input (which Docker host to query, with implications for openWorld behavior) yet the description gives no hint of its meaning, format, or whether omitting it targets all servers.

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?

The description is the literal endpoint string 'GET /docker.getContainers', which merely restates the tool name in HTTP terms. It conveys 'fetch containers' but supplies no scope, filtering behavior, or distinction from near-identical siblings like docker-getContainersByAppLabel or docker-getServiceContainersByAppName, which an agent cannot tell apart from this text.

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 when-to-use guidance, no exclusion of alternatives, and no stated preconditions. The presence of five container-listing siblings makes the absence of routing guidance a real selection hazard, but the text is not actively misleading, so a 2 rather than a 1.

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