Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-getDockerDiskUsage

Read-onlyIdempotent

Retrieves Docker disk usage from a Dokploy instance to help monitor storage consumption and identify space usage.

Instructions

GET /settings.getDockerDiskUsage

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, covering the safety profile, but the description adds no behavioral context of its own — no indication of what the call reads, whether it queries the local Docker daemon, or what the response contains. It contributes nothing beyond the structured fields.

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 single line is short but conveys no information beyond the tool name, so its brevity reflects under-specification rather than efficient structure. There is no front-loaded statement of purpose.

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?

With no output schema, the description carries the burden of explaining the return value, yet it says nothing about what disk-usage data is produced. Given several closely named siblings (dockerDiskUsage-getDiskUsage, settings-cleanDockerBuilder, settings-cleanDockerPrune), the definition is too thin for an agent to call it confidently.

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

Parameters4/5

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

The tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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 "GET /settings.getDockerDiskUsage", which restates the tool name in a different notation rather than explaining what it does. An agent learns that it is a read call to a settings endpoint, but nothing about what disk-usage information is returned or how it differs from 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 Guidelines2/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 mention of alternatives such as dockerDiskUsage-getDiskUsage, and no prerequisites or context. The agent must infer selection entirely from the tool 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