Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-deleteContainerFile

Destructive

Deletes a specified file inside a Docker container by container ID and path, letting you remove unwanted or stale files from running containers without manual shell access.

Instructions

POST /docker.deleteContainerFile

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

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 destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. However, the description adds nothing about what exactly gets destroyed, whether the deletion is reversible, whether the container must be running, or any permission requirements — which is a meaningful gap for a destructive mutation.

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 this is under-specification rather than conciseness. The single fragment carries no actionable information and is not front-loaded with purpose or constraints.

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?

A destructive, 3-parameter file-deletion tool with no output schema and zero schema descriptions demands explanatory content, and the description provides none. An agent has no basis to call it correctly beyond the endpoint string.

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% for three parameters (containerId, path, serverId), and the description supplies no meaning for any of them. Nothing indicates what path is relative to, whether serverId selects a remote host, or how containerId is resolved, so the agent must guess at required identifier formats.

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 an HTTP route restatement, "POST /docker.deleteContainerFile", which adds nothing beyond the tool name. It implies deletion of a file inside a container, but only because the name already says so; there is no stated scope, no distinction from siblings like docker-removeContainer or docker-writeContainerFile.

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 guidance at all on when to use this tool, when not to, or which sibling to prefer for related operations such as docker-removeContainer or dockerVolume-deleteVolumeFile. The agent must infer everything from the name.

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