Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerDiskUsage-getDiskUsage

Read-onlyIdempotent

Retrieves Docker disk usage for a specified server, helping you identify storage consumption and manage capacity.

Instructions

GET /dockerDiskUsage.getDiskUsage

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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, but the description adds nothing beyond that — it merely echoes an HTTP GET, which duplicates readOnlyHint. No mention of cost, latency, freshness of the reported figures, or whether serverId selects among multiple Docker servers in a way that changes results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short line with no padding, so it is concise, but it is a route echo rather than front-loaded explanatory content. Brevity here reflects under-specification, not efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one optional parameter, no output schema), but a disk-usage read is only useful if the agent knows what it returns and when it should be preferred over sibling reporting tools. With no return-value hint and no routing guidance, the definition is incomplete for selection even at low complexity.

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?

Schema description coverage is 0% for the single optional serverId parameter, so the schema provides a bare type with no meaning. The description does not explain what serverId identifies, whether omitting it targets a default server, or how it interacts with the Docker environment being inspected, leaving the gap entirely unaddressed.

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 HTTP route 'GET /dockerDiskUsage.getDiskUsage', which restates the tool name rather than explaining what it does. It implies retrieval of Docker disk usage, but gives no verb-object framing, no indication of what usage data (images, containers, volumes, build cache) is reported, and nothing to distinguish it from the sibling settings-getDockerDiskUsage.

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 alternatives such as settings-getDockerDiskUsage or dockerDiskUsage-getBuildCache. The agent must infer everything from the tool 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