Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerDiskUsage-pruneBuildCache

Idempotent

Prune Docker build cache to reclaim disk space on a Dokploy server. Removes unused build cache layers to reduce disk usage.

Instructions

POST /dockerDiskUsage.pruneBuildCache

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": "dockerDiskUsage-pruneBuildCache"
  }
}

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 supply only openWorldHint and idempotentHint; there is no destructiveHint even though pruning build cache deletes data. The description does nothing to fill that gap—no mention of what is destroyed, whether builds must be stopped, permission needs, or reclaim behavior.

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 only because it is under-specified—a bare route string rather than a front-loaded purpose statement. Brevity here is an absence of content, not efficiency.

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 destructive, server-scoped mutation with no output schema and an undocumented parameter, the definition provides nothing an agent needs to call it safely or 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?

One optional parameter (serverId) with 0% schema description coverage and no explanation in the description. Nothing indicates what happens when serverId is omitted or how it scopes the prune.

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 just the raw route "POST /dockerDiskUsage.pruneBuildCache"; it restates the tool name rather than stating in plain language what the operation does (presumably remove Docker build cache on a server). A reader can infer pruning from the name, but the description adds no verb+resource statement of its own.

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?

No when-to-use, when-not-to-use, or alternative guidance whatsoever. Siblings such as dockerDiskUsage-getBuildCache (inspection) and settings-cleanDockerPrune (a different cleanup path) exist, but nothing says which to pick or what precondition precedes a prune.

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