Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-listContainerFiles

Read-onlyIdempotent

List files and directories at a specified path inside a Docker container to inspect container contents without opening an interactive shell.

Instructions

GET /docker.listContainerFiles

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": {
      "containerId": "<containerId>",
      "path": "<path>"
    },
    "name": "docker-listContainerFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
serverIdNo
containerIdYes

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. The description adds nothing beyond that — no note on whether the path is a directory vs file, what happens on invalid paths, or the shape/limits of results. It does not contradict 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 short by omission rather than by discipline; the single opaque HTTP route string is not front-loaded guidance an agent can act on. Brevity here is under-specification, not conciseness.

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?

For a 3-parameter tool with zero schema documentation and no output schema, the description should carry the full explanatory burden. It carries none, leaving required parameters and return behavior entirely undocumented.

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% across three parameters (containerId, path, serverId), and the description supplies no meaning at all — not even whether path is absolute, relative to the container root, or must be a directory. This is the critical gap, since path semantics determine whether the call succeeds.

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 only restates the endpoint as "GET /docker.listContainerFiles", which is a tautology of the tool name. It conveys that files are listed over HTTP GET, but never states what is listed, from where, or how it differs from siblings such as docker-readContainerFile 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 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 preconditions, and no mention of alternatives like docker-readContainerFile for fetching a single file's contents. An agent must guess entirely from the name and the sibling list.

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