Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupPostgres

Idempotent

Triggers a manual backup of a PostgreSQL database in Dokploy using a backup ID. Use it to run an on-demand backup outside scheduled jobs.

Instructions

POST /backup.manualBackupPostgres

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

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 already declare idempotentHint=true and openWorldHint=true, so the safety profile is partly covered externally. The description adds nothing about what the POST triggers, whether the backup runs synchronously, whether an existing backupId overwrites prior state, or what happens on failure, which is exactly the context a caller needs for a mutation endpoint.

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 text is extremely short but not concise in the useful sense: a bare route with no front-loaded purpose sentence. It omits the information an agent needs instead of compressing it.

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 endpoint with one undocumented parameter, no output schema, and sibling tools that differ only by database engine, the definition supplies no operation semantics, no return expectations, and no disambiguation. It is not sufficient to invoke the tool correctly with confidence.

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% for the single required parameter backupId, so the description must compensate and it does not. It never explains whether backupId identifies an existing backup to run, names a new backup to create, or must be pre-generated by the caller.

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.manualBackupPostgres", which restates the tool name rather than stating what the tool does. An agent can guess it triggers a manual backup of a Postgres database, but nothing in the text says so, and it is not distinguished from the many sibling backup tools.

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 when to prefer this over backup-manualBackupMySql, backup-create, or the other manual backup variants. The route alone gives no selection criteria.

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