Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerVolume-getVolumes

Read-onlyIdempotent

Lists Docker volumes on a selected Dokploy server, helping you inspect available storage before managing deployments or infrastructure.

Instructions

GET /dockerVolume.getVolumes

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

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?

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that—no indication of whether results are server-scoped, whether there is pagination, or how volumes are keyed. It does not contradict the annotations, but it contributes no behavioral context.

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 brevity is under-specification, not efficiency—the entire text is a route echo with no informational content. There is no structure to front-load because there is nothing but the endpoint.

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?

For a simple one-parameter read tool with no output schema, the annotations carry the read-only profile, but the description never explains what a volume entry contains or how serverId changes scope. Substantial required information is missing even at this low complexity.

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% for the single parameter serverId, and the description says nothing about it. The agent cannot tell whether omitting serverId returns volumes across all servers or whether the parameter is required in practice.

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 string "GET /dockerVolume.getVolumes", which restates the tool name rather than describing the operation. An agent can guess it lists Docker volumes from the verb+path, but nothing distinguishes it from siblings like dockerVolume-getVolumesSize or dockerVolume-listVolumeFiles.

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?

No when-to-use context, no prerequisites, and no mention of alternatives such as getVolumesSize. The agent must infer from the name alone that this is the general volume-enumeration call.

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