Skip to main content
Glama

xo_list_tasks

Lists running and recent Xen Orchestra tasks, including migrations, backups, snapshots, and other operations, with status and progress percentage. Use it to monitor active and completed work.

Instructions

List running and recent tasks in Xen Orchestra.

Shows migrations, backups, snapshots, and other operations in progress with their status and progress percentage.

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

Input Schema

NameRequiredDescriptionDefault
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose that results include status and progress percentage, which is genuine behavioral value, but leaves the meaning of "recent" (time window or retention) and any pagination or scope limits undefined.

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?

Front-loaded with the core purpose in the first sentence, followed by concrete detail on returned fields. The trailing Args block is slightly formal for a single optional parameter but earns its place by documenting it.

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

Completeness4/5

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

For a one-parameter list tool with no output schema, disclosing status and progress percentage covers the main return-value question. The remaining gap is the undefined "recent" window and any result limits, which an agent would need to know for reliable use.

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 for the single parameter. It labels gateway_id as an optional "Target gateway", which is more than the schema's bare title, but it does not explain the default behavior when omitted or how scoping to a gateway changes results.

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 running and recent tasks in Xen Orchestra") plus the operation types surfaced (migrations, backups, snapshots). That implicitly separates it from siblings like xo_list_backups, but no alternative is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for monitoring in-flight and recent operations. There is no statement of when to prefer this over polling a specific resource tool, and no prerequisites or exclusions.

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