Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupMariadb

Idempotent

Triggers an on-demand backup of a MariaDB database in Dokploy using the specified backup ID, so you can create a fresh restore point without waiting for a scheduled run.

Instructions

POST /backup.manualBackupMariadb

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

Input Schema

NameRequiredDescriptionDefault
backupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so idempotency is covered structurally. The description adds nothing about what a manual backup entails — whether it blocks, where output is stored, how long it runs, or what permissions are needed — leaving the behavioral burden almost entirely unmet.

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?

The single line contains no filler, but it is under-specified rather than concise. A raw route string is not front-loaded functional information for an agent choosing a tool.

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, no parameter documentation, and only partial annotations, the description carries full responsibility for explaining the call and does none of it. An agent could not reliably predict the result of invoking this tool.

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, and the description says nothing about it. It is unclear whether backupId identifies the MariaDB service to back up, an existing backup record, or a naming key, which is a critical ambiguity for a one-parameter tool.

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.manualBackupMariadb", which restates the tool name rather than stating what the tool does. An agent must infer from the name alone that this triggers a manual MariaDB backup, and nothing in the text confirms the operation's effect.

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 use this tool, no prerequisites, and no mention of when to prefer it over siblings such as backup-manualBackupMySql or backup-create. The agent is left to guess entirely from naming conventions.

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