Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanDockerPrune

Idempotent

Prunes unused Docker resources on a specified Dokploy server to reclaim disk space and remove stale containers, images, and build cache.

Instructions

POST /settings.cleanDockerPrune

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

Input Schema

NameRequiredDescriptionDefault
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 declare openWorldHint and idempotentHint but notably do not declare destructiveHint, and the description does nothing to fill that gap — it never states that pruning deletes data or what scope is affected. The only behavioral signal is the endpoint path, which the agent already has as the tool name.

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 that brevity is under-specification rather than economy — a bare route string with no verb, object, or consequence. Nothing is front-loaded because there is no explanatory content at all.

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 mutation tool with no output schema, an undocumented optional parameter, and no destructive annotation, the description supplies none of the safety or scope information an agent needs. It is effectively an empty definition.

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 coverage is 0% for the single serverId parameter, so the description is the only place its meaning could be explained (which server to prune, default behavior when omitted). It says nothing, leaving an undocumented parameter on a destructive operation.

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.cleanDockerPrune', which merely restates the tool name. It never says what is pruned (images, containers, build cache, volumes) or what 'clean' means operationally, and it gives no basis for distinguishing it from siblings like settings-cleanUnusedImages or settings-cleanStoppedContainers.

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, no warning about irreversible removal, and no reference to any alternative tool. The agent has nothing to route on beyond guessing 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