Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-writeContainerFile

Idempotent

Writes or updates a file inside a Docker container by specifying the container ID, target path, and content.

Instructions

POST /docker.writeContainerFile

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>",
      "content": "<content>"
    },
    "name": "docker-writeContainerFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
contentYes
serverIdNo
containerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the description needs only to add context. It adds nothing — notably it never says whether an existing file at `path` is overwritten, what happens if the parent directory is missing, whether the container is touched, or how large a `content` payload is acceptable. For a filesystem mutation with no destructiveHint, that silence is a real gap.

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 certainly short, but the brevity is under-specification rather than economy — the single line contains no information an agent could act on beyond the tool's own name. Front-loading is irrelevant when there is nothing substantive to front-load.

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?

With three required parameters, a destructive filesystem effect, no output schema, and no annotation covering write semantics, the definition should explain far more than it does. The only reason this is not a 1 is that the tool name and idempotentHint together convey roughly what operation occurs.

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 four parameters, so the description carries the full burden and does not meet it. Nothing explains what `containerId` vs `serverId` select, whether `path` is absolute or relative to a working directory, or whether `content` is raw text versus encoded data.

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 "POST /docker.writeContainerFile", which restates the tool name and HTTP method rather than stating in plain terms that it writes a file into a running container. A reader can infer a write-file operation from the name alone, but the description itself contributes no verb/resource phrasing or scope, and does not distinguish it from siblings like docker-uploadFileToContainer or dockerVolume-writeVolumeFile.

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 (container must exist/running, permissions), and no routing to alternatives such as docker-uploadFileToContainer or dockerVolume-writeVolumeFile. The agent must guess from sibling names alone.

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