Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanDockerBuilder

Idempotent

Clears the Docker builder cache for a specified server to free disk space and resolve build issues. Use it to reset stale builder state before redeploying.

Instructions

POST /settings.cleanDockerBuilder

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations only declare openWorldHint and idempotentHint; there is no destructiveHint, so the description must explain what gets removed and whether it is recoverable, and it does none of that. A cache-clearing operation with zero disclosure of impact, preconditions, or side effects leaves the agent unable to judge risk.

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 a single route token, so it is not verbose, but the brevity here is under-specification rather than conciseness. There is no front-loaded statement of what the tool accomplishes.

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 state-changing cleanup operation with no output schema, no parameter documentation, and only two weak annotations, the definition gives an agent essentially nothing to act on. It should state what is cleaned, whether it is reversible, and what serverId controls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional parameter serverId has 0% schema description coverage, and the description adds no meaning at all — not even whether omitting it scopes to all servers or the local one. With only one parameter the gap is small, but nothing compensates for the missing semantics.

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.cleanDockerBuilder', which restates the tool name rather than explaining the action. An agent can infer that it clears Docker builder cache, but the definition never says so in plain terms, nor does it distinguish this from siblings like settings-cleanDockerPrune or settings-cleanUnusedImages.

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 on when to use this tool, when not to, or which sibling to prefer for related cleanup tasks. The agent must guess from the name alone whether this is a cache purge, a prune, or something broader.

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