Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerDiskUsage-getBuildCache

Read-onlyIdempotent

Retrieves Docker build cache disk usage for a Dokploy server so you can see how much space cached build layers consume.

Instructions

GET /dockerDiskUsage.getBuildCache

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

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 already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered elsewhere. The description adds nothing beyond the annotations — no statement of what scope of build cache is reported, whether the result is aggregated per server, or what a call costs.

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 brevity here comes from omission rather than discipline; the single fragment carries no usable information and is not front-loaded with purpose.

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 tool with an undocumented parameter, no output schema, and a name that is ambiguous against several disk-usage siblings, the description supplies none of the context needed to invoke it 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?

Schema description coverage is 0% and the single parameter serverId is undocumented in both schema and description. The description does not say whether serverId is optional, what a missing value implies, or which server is queried by default.

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 string "GET /dockerDiskUsage.getBuildCache", which restates the tool name as an HTTP path. It implies a read of build-cache disk usage but never states in prose what the tool returns or how it differs from the sibling dockerDiskUsage-getDiskUsage.

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 or when-not-to-use guidance, no mention of the related pruneBuildCache or getDiskUsage tools, and no prerequisites. An agent must infer everything about selection from the name alone.

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