Skip to main content
Glama
MCP Dokploy Online
by igoruam

volumeBackups-delete

Destructive

Deletes a volume backup by its ID, removing the specified backup record from Dokploy.

Instructions

POST /volumeBackups.delete

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": {
      "volumeBackupId": "<volumeBackupId>"
    },
    "name": "volumeBackups-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeBackupIdYes

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?

The annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds no behavioral context of its own — nothing about irreversibility, whether dependent backups or schedules are affected, or any confirmation requirements.

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 that brevity comes from under-specification rather than from tight editing. A raw route string is not front-loaded human-readable 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 single-parameter mutation tool with no output schema and 0% parameter coverage, the description supplies nothing an agent needs to call it safely or correctly. It is functionally a name echo.

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%, so the single required parameter volumeBackupId is undocumented in the schema. The description offers no explanation of what the ID refers to or how to obtain it, leaving the parameter entirely unilluminated.

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 the raw HTTP route "POST /volumeBackups.delete", which only restates the tool name with a verb and resource encoded as a path. It does not state in plain language that it deletes a volume backup, nor does it distinguish this from siblings such as volumeBackups-update or volumeBackups-list.

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 mention of alternatives such as volumeBackups-update or volumeBackups-runManually. The agent must infer usage entirely from the tool 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