Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanStoppedContainers

Idempotent

Removes stopped containers from a Dokploy server to reclaim disk space and keep infrastructure clean.

Instructions

POST /settings.cleanStoppedContainers

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": "settings-cleanStoppedContainers"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply idempotentHint and openWorldHint, but the description adds nothing about what is removed, whether removal is reversible, what permissions or target server are involved, or what is returned. For a destructive disk-cleanup operation, that is a serious disclosure gap.

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 text is short, but brevity here is under-specification rather than concision: a bare route string with no front-loaded purpose, scope, or effect. There is no structure to speak of.

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?

With no output schema, no annotation coverage of side effects, an undocumented parameter, and many near-identical cleanup siblings, the definition should explain scope and effect. It supplies none of that, so it is not sufficient to call correctly.

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?

The single parameter serverId has 0% schema description coverage, and the description does not mention it at all. Nothing indicates whether serverId scopes the cleanup to one host or is optional, leaving the only input undocumented in both places.

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 'POST /settings.cleanStoppedContainers', which restates the tool name as an HTTP route rather than stating what the tool does. An agent can infer 'remove stopped containers' from the name alone, but the description itself adds no verb, resource, or scope semantics.

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 preconditions, and no differentiation from closely related siblings such as settings-cleanAll, settings-cleanDockerPrune, settings-cleanUnusedImages, or settings-cleanUnusedVolumes. The agent must guess which cleanup tool applies.

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