Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerVolume-deleteVolumeFile

Destructive

Deletes a specified file from a Docker volume using its volume name and path, removing unwanted or stale data through Dokploy.

Instructions

POST /dockerVolume.deleteVolumeFile

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

Input Schema

NameRequiredDescriptionDefault
pathYes
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 destructiveHint=true and openWorldHint=true, so the safety profile is carried by structured data. The description adds nothing: no statement that the file is permanently removed, no permission or volume-state requirements, and no indication of what a successful POST returns.

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?

Extremely short, but this is under-specification rather than conciseness; there is no front-loaded statement of purpose beyond a route string. No sentence in it earns meaningful space because none carries 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?

For a destructive, three-parameter mutation tool with no output schema and zero schema documentation, the definition is wholly inadequate. Nothing tells the agent about irreversibility, prerequisites, or results.

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% with three parameters (volumeName, path, serverId), and the description explains none of them. It does not clarify path format, whether volumeName must exist, or what serverId selects.

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 HTTP route "POST /dockerVolume.deleteVolumeFile", which restates the tool name rather than describing the operation. An agent can infer a delete of a file within a named volume only from the tool name, not from the description text.

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?

No guidance on when to use this versus docker-deleteContainerFile, dockerVolume-writeVolumeFile, or volumeBackups-delete. The destructive nature implied by 'delete' is never stated as a precondition or caution.

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