Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerVolume-listVolumeFiles

Read-onlyIdempotent

List files and directories inside a Docker volume at a specified path, optionally on a chosen server, to inspect volume contents.

Instructions

GET /dockerVolume.listVolumeFiles

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "volumeName": "<volumeName>",
      "path": "<path>"
    },
    "name": "dockerVolume-listVolumeFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
serverIdNo
volumeNameYes

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=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered and the description does not contradict it. However, the description adds nothing beyond that: nothing about recursion, whether directories are included, pagination, error behavior for a missing volume or path, or how large listings behave.

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 reflects under-specification rather than concision; the single endpoint token earns no useful information for an agent deciding whether and how to call the tool.

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?

A three-parameter, required-input list operation with no output schema and no documented parameters needs the description to carry the full burden. Instead it offers a bare route string, leaving the agent unable to predict what is returned or how to form a valid path argument.

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 description provides no parameter information at all. The meaning of "path" (absolute vs relative to volume root, directory vs file, maxLength 4096) and of "serverId" (optional targeting of a remote Docker host) is left entirely unexplained.

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 endpoint string "GET /dockerVolume.listVolumeFiles", which restates the tool name and implies a read of volume files. It conveys no scope, no return shape, and does nothing to distinguish this from siblings such as dockerVolume-readVolumeFile or dockerVolume-deleteVolumeFile beyond the vague word "list".

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 prerequisites, and no indication of how this differs from readVolumeFile, listContainerFiles, or the backup listing tools. An agent must guess entirely from the 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