Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-uploadFileToContainer

Idempotent

Upload files directly into a running Docker container to update configuration, add assets, or place resources without rebuilding the image.

Instructions

POST /docker.uploadFileToContainer

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docker-uploadFileToContainer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

The annotations only declare openWorldHint=true and idempotentHint=true. The description adds nothing beyond the HTTP verb: it does not say whether existing files are overwritten, what auth or access is needed, where the file lands, or how errors surface. For a write operation, this leaves far too much behavior undisclosed, even allowing for the lower bar that annotations set.

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 brevity here reflects under-specification rather than conciseness: a bare route path is not front-loaded guidance. The one line of text carries no useful information for invocation.

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?

There is no output schema, no annotations that describe the operation's effects, and no explanation of how a zero-parameter upload is even performed. An agent has no basis to call this tool correctly, so the definition is incomplete for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero properties with additionalProperties=false, so by default the baseline is 4. But for a file-upload tool, the definition never explains how the file content, target container, or destination path are supplied, which is the single most important thing an agent must know. That unexplained gap, not the schema itself, is why this cannot score above a 3.

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 route string "POST /docker.uploadFileToContainer", which restates the tool name and adds only the HTTP method. It does not say what is uploaded from where, or what distinguishes it from siblings like docker-writeContainerFile, so an agent gets no real purpose statement beyond the name.

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 at all. With closely related siblings such as docker-writeContainerFile and docker-deleteContainerFile available, the definition offers no criteria for choosing this tool over them and no prerequisites.

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