Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerVolume-writeVolumeFile

Idempotent

Writes or updates a file inside a specified Docker volume on a Dokploy server, so you can manage volume content directly without accessing a container.

Instructions

POST /dockerVolume.writeVolumeFile

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>",
      "content": "<content>"
    },
    "name": "dockerVolume-writeVolumeFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
contentYes
serverIdNo
volumeNameYes

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 openWorldHint=true and idempotentHint=true, so the safety/mutability profile is partly covered structurally. The description contributes nothing further – it does not say whether an existing file at 'path' is overwritten, whether parent directories are created, what permissions are applied, or what happens on failure.

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 one-line endpoint string is trivially short but is under-specification rather than conciseness. There is no front-loaded explanation of purpose, so the brevity costs the agent needed information.

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?

This is a content-writing mutation tool with an undocumented four-parameter schema, no output schema, and a serverId that presumably picks the target host. With annotations covering only openWorld/idempotent hints, an endpoint string leaves the definition materially incomplete for correct invocation.

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 of explaining volumeName, path, content, and serverId. It provides zero parameter semantics – no format, path-rooting, encoding, or serverId targeting behavior.

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 route 'POST /dockerVolume.writeVolumeFile', which restates the tool name rather than stating what the tool does in prose. An agent can infer from the name that it writes a file into a Docker volume, but the description itself adds no verb-and-resource explanation beyond the identifier.

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 guidance on when to use this rather than docker-writeContainerFile, dockerVolume-readVolumeFile, or docker-uploadFileToContainer. The only implicit signal is the 'write' verb and 'Volume' scope in the name, which is name-inference rather than stated guidance.

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