Skip to main content
Glama
MCP Dokploy Online
by igoruam

rollback-delete

Destructive

Permanently deletes a specific Dokploy deployment rollback by its rollback ID, removing the saved restore point when it is no longer needed.

Instructions

POST /rollback.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": {
      "rollbackId": "<rollbackId>"
    },
    "name": "rollback-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
rollbackIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds nothing on top: no statement of what is irreversibly destroyed, whether dependent deployments or history are affected, or whether the operation can be undone. It provides only a transport method, which is the thinnest possible disclosure 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 the brevity comes from under-specification rather than efficiency; a bare route string is not front-loaded with the information an agent needs. There is no structure beyond the HTTP verb and path.

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, open-world mutation with one undocumented required parameter and no output schema, the description supplies none of the missing context. An agent cannot determine scope, side effects, or failure modes from 'POST /rollback.delete'.

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?

The single required parameter rollbackId has 0% schema description coverage, and the description does not compensate at all — it never explains what a rollbackId identifies or how an agent obtains one. The schema only constrains it to a non-empty string.

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 an HTTP route signature, 'POST /rollback.delete', which restates the tool name rather than explaining what is being deleted. It never says whether the rollback record itself is removed, whether a deployed state is reverted, or what a rollback is in this system.

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 the many sibling delete tools (rollback-rollback, previewDeployment-delete, patch-delete, etc.). Nothing states prerequisites, such as requiring an existing completed rollback or elevated permissions, or any when-not-to-use condition.

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