Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupWebServer

Idempotent

Triggers a manual backup of a web server configuration and data by backup ID, so you can create an on-demand restore point outside scheduled backups.

Instructions

POST /backup.manualBackupWebServer

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": {
      "backupId": "<backupId>"
    },
    "name": "backup-manualBackupWebServer"
  }
}

Input Schema

NameRequiredDescriptionDefault
backupIdYes

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 supply only openWorldHint=true and idempotentHint=true; they say nothing about side effects, required permissions, or what is written where. The description adds nothing beyond the raw route — it does not disclose whether a backup artifact is created, where it lands, whether it can be repeated safely, or what the call returns.

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 certainly short, but that brevity comes from under-specification rather than efficiency — a single endpoint string that conveys almost no meaning. There is no front-loaded statement of purpose for an agent to act 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?

For a mutating backup tool with one undocumented parameter, no output schema, and thin annotations, the description should explain the target, the effect, and the identifier. None of that is present, leaving the definition inadequate to call the tool correctly.

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 required parameter (backupId) with 0% schema description coverage, so the description bears full responsibility for explaining it. It contributes nothing: no hint about whether backupId names the server, the target, or a new backup record, nor any format information.

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 route string "POST /backup.manualBackupWebServer", which restates the tool name as an HTTP method plus path. It hints that a manual backup of the web server is triggered, but gives no verb-level statement of what the operation actually does or how it differs from siblings like backup-manualBackupCompose or backup-create.

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 mention of prerequisites, no exclusions, and no reference to alternatives such as the other manual backup tools or the scheduled backup tools. The reader is left to infer everything from the path fragment.

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