Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getContainersByAppLabel

Read-onlyIdempotent

Retrieve Docker containers by application name and deployment type (standalone or swarm) to inspect app-specific containers on a Dokploy server.

Instructions

GET /docker.getContainersByAppLabel

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": {
      "appName": "<appName>",
      "type": "<type>"
    },
    "name": "docker-getContainersByAppLabel"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
appNameYes
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — it says nothing about what a label lookup returns, whether results are scoped to a server, or what happens when no containers match.

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?

It is a single short line with no wasted words, but this is under-specification rather than conciseness — the one sentence carries no usable information. Front-loading is moot when there is nothing substantive to front-load.

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?

For a three-parameter, two-required tool with no output schema and zero schema description coverage, the definition is completely inadequate — it provides no parameters, no return behavior, and no routing cues. Nothing an agent needs to invoke it correctly is present.

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% for three parameters (appName, type, serverId), and the description supplies no compensating meaning for any of them. For example, nothing explains whether 'type' selects the container runtime context or how serverId relates to the lookup, which is exactly the gap the description must fill here.

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 text is only 'GET /docker.getContainersByAppLabel', which restates the tool name as a REST route without stating in prose what the tool retrieves or how it differs from siblings like docker-getContainersByAppNameMatch or docker-getContainers. An agent must infer 'fetch containers by app label' purely from the identifier.

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 mention of when to prefer a sibling such as docker-getContainersByAppNameMatch, and no prerequisites. The name hints at label-based lookup but the definition never states the selection condition.

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