Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getStackContainersByAppName

Read-onlyIdempotent

Retrieve Docker stack containers for a specified application name, optionally scoped to a server, to inspect or manage a Dokploy deployment.

Instructions

GET /docker.getStackContainersByAppName

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>"
    },
    "name": "docker-getStackContainersByAppName"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
serverIdNo

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 readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered by structured data. The description adds no behavioral context at all — no note on whether serverId scoping changes results, no error behavior for unknown apps, no pagination or volume of results for an open-world endpoint.

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 short, but only because it is under-specified; the single route token conveys no meaning to an agent that cannot see the HTTP layer. There is no structure, no front-loaded purpose statement, and nothing that earns its place.

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 two-parameter lookup with no output schema and no parameter documentation, the description should carry the full burden and does not. An agent cannot determine what the call returns, how results are scoped, or how to choose the right sibling tool.

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 both parameters, and the description compensates for none of it. It never clarifies that appName identifies a Docker Compose stack, nor what serverId does or whether omitting it defaults to a local/all server.

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 only the route string "GET /docker.getStackContainersByAppName", which restates the tool name rather than stating in plain language what it does. It does not explain what a "stack" is here or what container data is returned, so an agent must infer everything from the name.

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, no prerequisites, and no mention of when to prefer this over the closely named siblings such as docker-getServiceContainersByAppName or docker-getContainersByAppNameMatch. The agent is left to guess from name similarity alone.

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