Skip to main content
Glama
MCP Dokploy Online
by igoruam

dockerVolume-removeVolume

Destructive

Remove a specified Docker volume from a Dokploy server to clean up unused storage. Use it to delete persistent volume data by volume name.

Instructions

POST /dockerVolume.removeVolume

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo
volumeNameYes

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 carried by structured data. The description adds nothing: it does not say data is lost, whether a volume must be detached from containers first, or which server the operation hits — so it merely echoes the endpoint.

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?

A single endpoint string is technically brief, but it is under-specification rather than conciseness — there is no front-loaded statement of effect or scope. Brevity here costs the agent all needed context.

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, cross-server mutation with zero schema descriptions and no output schema needs the description to carry warnings and parameter meaning. Instead the definition supplies none of that, leaving an agent unable to distinguish it from sibling removal tools.

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 two parameters, and the description adds no meaning for volumeName or serverId. Critically, it does not explain whether serverId defaults to the local node or that volumeName must match the pattern-constrained identifier.

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 method and path, "POST /dockerVolume.removeVolume". It implies deletion of a Docker volume, but this is inferred from the tool name and path rather than stated as a verb+resource sentence, and it draws no boundary against volumeBackups-delete, dockerVolume-deleteVolumeFile, or backup-remove.

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 on when to call this versus alternatives such as volumeBackups-delete or dockerVolume-deleteVolumeFile, and no warning that removal is destructive. The agent has to infer applicability entirely 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