Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanUnusedVolumes

Idempotent

Deletes unused Docker volumes on a specified Dokploy server to reclaim storage and reduce orphaned volume buildup.

Instructions

POST /settings.cleanUnusedVolumes

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": "settings-cleanUnusedVolumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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 supply openWorldHint and idempotentHint, but neither declares destructiveness — and deleting volumes is inherently destructive and irreversible. The description adds no warning about data loss, required permissions, or whether removal is scoped or global, so it contributes nothing beyond the annotation block.

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 only because it is a raw endpoint string rather than an explanatory sentence. Being brief is not a virtue here since nothing useful is front-loaded for the agent.

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, open-world maintenance tool with an undocumented parameter, no output schema, and no annotations covering destructiveness needs substantially more description than one HTTP route line. An agent lacks the information required to invoke it safely.

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?

There is one optional parameter, serverId, at 0% schema description coverage. The description does not mention it at all, so the agent cannot tell whether omitting it means 'all servers' or a default server — a meaningful ambiguity for a destructive operation.

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?

"POST /settings.cleanUnusedVolumes" merely restates the tool name as an HTTP route. It implies volume cleanup, but says nothing about scope (all servers vs. one), what counts as 'unused', or how this differs from settings-cleanAll or dockerVolume-getVolumes.

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, no prerequisites, and no named alternative. An agent gets zero help deciding between this and the many sibling clean tools (cleanUnusedImages, cleanStoppedContainers, cleanAll, cleanDockerPrune).

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