Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupCompose

Idempotent

Triggers a manual backup for a Docker Compose stack by backup ID, letting you create an on-demand restore point in Dokploy.

Instructions

POST /backup.manualBackupCompose

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

Input Schema

NameRequiredDescriptionDefault
backupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations provide only openWorldHint and idempotentHint, leaving the safety profile (readOnly/destructive) undeclared, so the description must carry the burden and does not. The bare 'POST' implies a state-changing call, but there is no disclosure of side effects, whether the backup runs synchronously or asynchronously, permission needs, or what happens on repeat invocation.

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 a single short line with no filler words, but this is under-specification rather than conciseness — the one line conveys no information beyond the tool name and route. There is no front-loaded statement of purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and no annotations covering safety, the definition is far too thin. Nothing tells the agent what the call returns, how long it takes, or how to interpret success, which an agent needs before triggering a backup operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is expected to compensate, yet it never mentions backupId. It is ambiguous whether backupId identifies the Compose project, an existing backup record, or a configuration, and the description supplies no clarification.

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.manualBackupCompose', which essentially restates the tool name rather than explaining what the call accomplishes. An agent can infer it triggers a manual backup for a Compose project, but nothing distinguishes it from the sibling backup-manualBackup* variants (MySql, Mongo, Postgres, etc.) or states what 'manual backup compose' actually does.

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. The agent must guess whether this is preferred over backup-create or compose-deploy for snapshotting a Compose deployment.

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