Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-getBackups

Read-onlyIdempotent

Retrieves the backups associated with the authenticated Dokploy user so you can review available backup records and plan recovery.

Instructions

GET /user.getBackups

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "user-getBackups"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is fully carried by structured data. The description adds nothing beyond that — no disclosure of what data is returned, whether results are paginated or filtered to the caller, or what 'open world' means in this context.

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 with no wasted clauses, but it is a bare endpoint fragment rather than a description, so there is no front-loaded statement of purpose or scope. The brevity here reflects under-specification rather than disciplined conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The invocation surface is trivial (no params), so an agent can technically call it, but there is no output schema and no description of the return shape — fields, counts, or size of backup listings. With many sibling backup tools present, the definition is too thin to tell an agent what it will actually get back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object with additionalProperties=false, so there is no parameter meaning for the description to add. Baseline 4 applies for a no-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 the raw endpoint string 'GET /user.getBackups', which essentially restates the tool name in HTTP verb form. It conveys that this is a read of backups tied to a user, but nothing about what a 'backup' is here, what scope (own account vs. all users) is covered, or how it differs from siblings such as overview-backups or volumeBackups-list.

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 when-to-use guidance, no stated preconditions, and no mention of any alternative tool. An agent choosing between this and the multiple backup-related siblings (overview-backups, volumeBackups-list, volumeBackups-one) gets no routing signal whatsoever from the description.

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