Skip to main content
Glama

xo_list_backups

List Xen Orchestra backup jobs to review configured job names, backup modes (full, delta, disaster recovery), and enabled status, optionally filtered by gateway.

Instructions

List backup jobs configured in Xen Orchestra.

Shows job name, mode (full, delta, disaster recovery), and enabled status.

Args: gateway_id: Target gateway (optional).

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": "xo_list_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'List' implies a safe read and the mode values (full, delta, disaster recovery) plus enabled status give useful shape to the result, but there is no statement about permissions, pagination, ordering, or whether filtering by mode is possible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences plus a one-line arg note, with the core purpose front-loaded. The 'Args:' block is slightly redundant with the schema but is not wasteful.

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

Completeness3/5

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

For a single-optional-parameter list tool with no output schema, the description covers purpose and return fields adequately. It falls short on the gateway_id default behavior and on any pagination/volume expectations, which matter for a backup inventory that could be large.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does explain that gateway_id is optional and what it points at ('Target gateway'), but it does not say what happens when it is omitted (e.g., default gateway) or what form of identifier is expected.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List backup jobs configured in Xen Orchestra') and even names the fields returned (name, mode, enabled status). It is clearly distinguishable from action siblings like xo_run_backup or xo_restore_backup by being a read-only listing, though it never names those siblings explicitly.

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 or when-not-to-use guidance, and no mention of alternatives such as xo_run_backup or xo_restore_backup. The agent must infer that this is the discovery step before those actions; nothing in the text says so.

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