Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-manualBackupMongo

Idempotent

Triggers an on-demand MongoDB backup for a specified Dokploy backup ID, enabling manual backup creation when a scheduled backup has not run or is needed immediately.

Instructions

POST /backup.manualBackupMongo

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

Input Schema

NameRequiredDescriptionDefault
backupIdYes

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 only supply openWorldHint and idempotentHint; the description adds nothing about what the backup operation does, where artifacts go, whether it is blocking, what happens on failure, or what permissions are needed. For a stateful mutation with zero annotation coverage of safety or effects, this is a serious gap.

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; an endpoint string is not front-loaded explanatory content.

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 useful annotations, and an undocumented required parameter, the definition leaves an agent unable to tell what a successful or failed call looks like or what the backupId refers to.

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?

The single required parameter backupId has 0% schema description coverage, and the description provides no meaning, format, or constraints for it beyond the schema's minLength.

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 endpoint 'POST /backup.manualBackupMongo', which restates the tool name without explaining what a manual Mongo backup does, what it produces, or how it differs from sibling backup tools like backup-create or backup-manualBackupPostgres.

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?

No guidance at all on when to use this versus the many sibling backup tools (create, update, listBackupFiles) or per-database manual backup variants; the agent must infer everything from the name.

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