Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-one

Read-onlyIdempotent

Retrieves details for a single Dokploy backup using its backupId, so you can inspect a specific backup record.

Instructions

GET /backup.one

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

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 readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered without the description. The description adds nothing beyond that: no statement of what is returned, whether a missing backup yields an error, or what the openWorld network call reaches.

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 brief, but the brevity comes from under-specification rather than from efficient wording. A raw method-plus-path line is not a useful front-loaded statement of purpose for an agent.

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, an undocumented required parameter, and no annotations covering return behavior, the description carries the full burden and provides none of it. An agent cannot tell from this text what it will receive or what backupId must be.

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% and the single required parameter backupId is completely undocumented. The description does not say where a backupId comes from, what format it takes, or that it identifies exactly one backup, leaving the only non-obvious part of the call unexplained.

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?

"GET /backup.one" restates the tool name with an HTTP verb and path; the only added signal is that it is a read. It never says what a "backup.one" is (a single backup record retrieved by ID) or how it differs from backup-listBackupFiles or the backup-* creation 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 prerequisite, and no mention of an alternative such as listing backups or fetching backup files. At best the GET verb weakly implies retrieval of an existing resource.

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