Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupMySql

Idempotent

Triggers a manual MySQL backup for a specified backup ID via Dokploy, allowing users to create an on-demand backup when needed.

Instructions

POST /backup.manualBackupMySql

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

Input Schema

NameRequiredDescriptionDefault
backupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations only supply openWorldHint=true and idempotentHint=true; they say nothing about whether this creates a job, blocks until completion, requires credentials, or how failures surface. The description adds no behavioral context at all — it neither confirms nor contradicts the annotations.

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 efficiency: a bare route string carries almost no information for an agent. There is no front-loaded purpose statement.

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 write-style operation with an undocumented required parameter, no output schema, and thin annotations, the description is entirely inadequate. An agent has no basis to know what the call does with backupId or what a successful response means.

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 single required parameter backupId is documented nowhere. The description does not explain whether it is a caller-supplied idempotency key, an existing backup identifier, or a target reference — a meaningful gap for a mutation call.

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 REST route "POST /backup.manualBackupMySql", which restates the tool name rather than explaining the action. An agent can infer it triggers a manual MySQL backup, but nothing states the verb, scope, or how it differs from siblings like backup-manualBackupPostgres 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 Guidelines2/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 such as scheduled backups or other engine-specific backup tools. The only signal is the endpoint name, leaving the agent to guess.

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