Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getServiceContainersByAppName

Read-onlyIdempotent

Retrieve Docker service containers by application name, optionally scoped to a server ID, to inspect running services.

Instructions

GET /docker.getServiceContainersByAppName

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

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 without help from the description. The description adds nothing beyond them: no indication of return shape, pagination, error behavior when appName is unknown, or what serverId scoping does.

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 single line is short but is under-specification rather than conciseness; it is a route label, not a description. Nothing is front-loaded because nothing informative is present.

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 tool with two parameters, one required, zero schema documentation, and no output schema, the description supplies none of the missing context. An agent cannot reliably determine what it returns or how to scope the call.

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, so the description carries the full burden and fails entirely. It says nothing about the appName pattern/format expectations or what serverId selects, leaving both parameters semantically opaque.

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 only restates the endpoint path "GET /docker.getServiceContainersByAppName", which is essentially the tool name reformatted. It conveys no more than the name already does: no statement of what a "service container" is or how results differ from sibling tools such as docker-getContainersByAppNameMatch or docker-getStackContainersByAppName.

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 guidance whatsoever on when to use this tool versus the many closely named siblings. An agent must guess whether this returns containers for a compose service, a swarm service, or an app, and gets no prerequisites or exclusions.

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