Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerVolume-getVolumesSize

Read-onlyIdempotent

Retrieves the size of all Docker volumes on a specified Dokploy server, helping you monitor storage usage and identify volumes consuming disk space.

Instructions

GET /dockerVolume.getVolumesSize

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": "dockerVolume-getVolumesSize"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing: it does not say that the call reaches a live Docker server identified by serverId, nor what a failure or unknown server yields, so no behavioral value beyond the annotations.

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 that is under-specification rather than conciseness; the single line is a bare route with no front-loaded explanation of what is returned or how to call it.

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?

No output schema exists, so the description should explain the return shape (volumes and their sizes), and it does not. Combined with the undocumented serverId parameter and absent usage guidance, the definition is inadequate for even a one-parameter tool.

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 parameter serverId has 0% schema description coverage, and the description never mentions it or explains that it selects which Docker server/endpoint is queried. With low coverage the description was expected to compensate and it does not.

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 /dockerVolume.getVolumesSize", which essentially restates the tool name. It hints at a volume-size resource but never states in plain language that it returns the size/usage of Docker volumes, and it does nothing to distinguish itself from siblings like dockerDiskUsage-getDiskUsage or dockerVolume-getVolumes.

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 mention of prerequisites, and no reference to any alternative such as dockerVolume-getVolumes (listing) or dockerDiskUsage-getDiskUsage (disk usage). The agent is left to infer everything from the endpoint 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