Skip to main content
Glama
MCP Dokploy Online
by igoruam

rollback-rollback

Idempotent

Revert a Dokploy deployment by passing its rollback ID, restoring a prior release when changes must be undone.

Instructions

POST /rollback.rollback

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-rollback"
  }
}

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 openWorldHint=true and idempotentHint=true, and the description adds nothing beyond them. It does not disclose what state is mutated, whether the rollback is reversible, what permissions are needed, or what happens if the rollbackId is stale or already applied – all critical for a mutation endpoint with no destructiveHint.

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 efficient wording. A raw route string is not a front-loaded explanation of purpose, so there is nothing for the agent to anchor on.

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?

With no output schema, a mutation endpoint, an undocumented required parameter, and thin annotations, the description carries the full burden and delivers essentially nothing. An agent cannot safely determine effect, return value, or failure modes from this definition.

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% for the single required parameter rollbackId, so the description must compensate and does not. It never explains what identifies a rollback (an ID of a rollback record, a deployment to revert, a job token) or its expected format.

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 /rollback.rollback" only restates the tool name as an HTTP method plus route. It conveys that this is a write-style POST to a rollback endpoint, but never states what a rollback actually does (revert a deployment? undo a config change?) or how it differs from the sibling rollback-delete.

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 preconditions, and no mention of alternatives such as rollback-delete. The only signal an agent has is the HTTP verb, which is not enough to choose between the rollback-related siblings.

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