Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateDockerCleanup

Idempotent

Enable or disable Docker cleanup for a Dokploy instance or specific server to control automatic removal of unused containers and images.

Instructions

POST /settings.updateDockerCleanup

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": {
      "enableDockerCleanup": "<enableDockerCleanup>"
    },
    "name": "settings-updateDockerCleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
enableDockerCleanupYes

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 already declare idempotentHint=true and openWorldHint=true, and the description adds nothing beyond them—no note on what cleanup actually removes, whether it affects running containers, required permissions, or scope by server. For a setting that can trigger destructive Docker cleanup, this silence is a serious gap; it does not contradict the annotations, merely fails to supplement them.

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 the brevity is under-specification rather than economy—the single route string earns no informational value. Nothing is front-loaded because there is essentially no content.

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 settings mutation with no output schema and no annotation coverage of reversibility or permission requirements, the description is completely inadequate. An agent cannot confidently call it without discovering behavior elsewhere.

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 supplies no compensating meaning: it does not say what enableDockerCleanup toggles or what serverId scopes (a specific node vs. default). An agent must guess whether omitting serverId means all servers or the local one.

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 "POST /settings.updateDockerCleanup", which restates the tool name and title rather than explaining what the operation does. It implies a settings mutation tied to Docker cleanup, but never states that it enables/disables automated Docker cleanup behavior, so an agent gets no more than the name already gives.

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 exclusions, and no mention of related siblings such as settings-cleanDockerPrune or settings-getDockerDiskUsage that an agent might reasonably confuse with this one. The agent must infer everything from the name.

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