Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-readContainerFile

Read-onlyIdempotent

Read a file from inside a Docker container by specifying the container ID and file path, letting you inspect application configuration or logs directly from your Dokploy instance.

Instructions

GET /docker.readContainerFile

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

Input Schema

NameRequiredDescriptionDefault
pathYes
serverIdNo
containerIdYes

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 safety semantics are covered structurally. The description contributes nothing beyond that: no mention of whether the container must be running, how paths are resolved inside the container, whether binary/large files are truncated or encoded, or what errors occur for missing paths. For a file-read tool these are material omissions, though there is no contradiction with 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?

The text is short with no padding, but it is under-specified rather than concise: a bare endpoint path is not front-loaded meaning. Length is not the issue; absence of substance is.

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?

With no output schema, three undescribed parameters, and only a route string, an agent lacks nearly everything needed to call this correctly. It cannot know the expected path semantics, error behavior, or return shape from this definition.

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), so the description carries the full burden of explaining them and explains none. It gives no hint about path format (absolute vs relative, working directory), what serverId selects, or the containerId pattern constraint.

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 route string "GET /docker.readContainerFile", which restates the tool name and HTTP verb rather than stating what the tool does in prose. An agent can infer a read of a file inside a Docker container from the name, but the description itself adds no verb+resource statement and does not distinguish it from siblings such as docker-listContainerFiles or dockerVolume-readVolumeFile.

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 prerequisites, and no mention of alternatives. The agent must guess how this differs from reading a volume file or listing container files, even though those siblings appear in the catalog.

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