Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-update

Idempotent

Modifies an existing Dokploy backup configuration, letting you change its schedule, destination, retention count, and enabled state to keep database backups aligned with current needs.

Instructions

POST /backup.update

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": {
      "schedule": "<schedule>",
      "enabled": "<enabled>",
      "prefix": "<prefix>",
      "backupId": "<backupId>",
      "destinationId": "<destinationId>",
      "database": "<database>",
      "keepLatestCount": "<keepLatestCount>",
      "serviceName": "<serviceName>",
      "databaseType": "<databaseType>"
    },
    "name": "backup-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixYes
enabledYes
backupIdYes
databaseYes
metadataNo
scheduleYes
serviceNameYes
databaseTypeYes
destinationIdYes
keepLatestCountYes
includeEncryptionKeyNo

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 idempotentHint=true and openWorldHint=true, so the safety/idempotency profile is covered by structured data. The description adds nothing beyond that — no statement of what fields are overwritten, whether omitted fields are reset, or what permissions are required for this 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 terse to the point of being empty; there is no wasted wording, but the single route token is under-specification rather than conciseness. Nothing is front-loaded because nothing substantive is stated.

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 mutation tool with 11 parameters, no output schema, no per-field documentation, and no destructive/irreversible-change disclosure, this definition is far too thin. An agent would have to guess at the payload semantics and side effects entirely from the schema.

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% across 11 parameters (9 required), including non-obvious ones such as includeEncryptionKey, keepLatestCount, serviceName, and the destinationId/databaseId relationships. The description contributes no parameter meaning whatsoever to compensate for the completely undocumented schema.

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 HTTP route "POST /backup.update", which restates the tool name and title rather than describing what is updated. It implies a mutation of a backup configuration but gives no resource detail, so an agent cannot distinguish it meaningfully from backup-create or backup-remove.

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 at all on when to use this tool versus backup-create, backup-remove, or the destination-update sibling, nor any stated preconditions. The route string carries no usage context.

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