Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getContainersByAppNameMatch

Read-onlyIdempotent

Retrieve Docker containers by matching an application name, with optional filters for app type and server ID, to identify containers tied to a specific app.

Instructions

GET /docker.getContainersByAppNameMatch

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

Input Schema

NameRequiredDescriptionDefault
appNameYes
appTypeNo
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=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered with no contradiction from the description. However, the description contributes nothing beyond them — no mention of match semantics (substring vs exact), result ordering, or whether multiple stacks can match a single appName.

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 one short line with no wasted words, but this is under-specification rather than conciseness. The single token is not front-loaded with any actionable information.

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 3-parameter tool with zero schema description coverage, no output schema, and ambiguous matching semantics, the definition provides nothing an agent needs to call it correctly. It is wholly inadequate relative to the tool's complexity.

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% and the schema only supplies types and a pattern for appName, plus an unexplained appType enum and serverId. The description supplies no meaning for any of the three parameters, so it fails to compensate for the coverage gap.

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 HTTP route 'GET /docker.getContainersByAppNameMatch', which restates the tool name rather than describing the operation in prose. An agent can infer 'list containers whose app name matches' from the name alone, but the description itself adds no verb/resource statement and does not distinguish this from siblings like docker-getContainers 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 when-to-use guidance, no mention of the near-identical siblings (getStackContainersByAppName, getServiceContainersByAppName, getContainersByAppLabel), and no indication of whether appType or serverId should be supplied. A route string cannot route the agent between alternatives.

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