Skip to main content
Glama
MCP Dokploy Online
by igoruam

volumeBackups-list

Read-onlyIdempotent

Lists volume backups for a specified resource ID and volume backup type, enabling review of available backups before restore or cleanup.

Instructions

GET /volumeBackups.list

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": {
      "id": "<id>",
      "volumeBackupType": "<volumeBackupType>"
    },
    "name": "volumeBackups-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
volumeBackupTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 structurally. The description adds nothing beyond that: no mention of pagination, result ordering, or whether the volumeBackupType filter is required to scope the listing.

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 short by omission rather than by efficiency; a raw endpoint string conveys no task-oriented information. Every element present is redundant with the tool name.

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?

A two-required-parameter listing endpoint with zero schema documentation and no output schema needs the description to explain inputs and result shape. Nothing here does, leaving the definition inadequate for correct invocation.

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 both required parameters, so the description carries the full burden and discharges none of it. It never explains that id is the volume identifier or that volumeBackupType selects the engine family to list.

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 method and path, "GET /volumeBackups.list", which essentially restates the tool name volumeBackups-list. It implies a listing operation but never says what is listed, in what shape, or how it differs from siblings like volumeBackups-one.

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 when-to-use guidance, no preconditions, and no routing to alternatives such as volumeBackups-one or volumeBackups-create. The agent must infer everything from the name alone.

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