Skip to main content
Glama
Sign In
AIops-tools

xcpng-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

task_list

Read-only

List Xen Orchestra tasks, optionally filtered by status, to monitor pending, successful, or failed operations and audit activity.

Instructions

[READ] List XO tasks, optionally filtered by status.

Returns {"tasks": [...], "returned": N, "limit": L, "truncated": bool}.
When truncated is true the task feed had more entries than were returned —
re-run with a higher limit or a narrower status filter.

Args:
    status: Optional filter: pending / success / failure.
    limit: Max tasks to return after filtering (default 200).
    target: Xen Orchestra target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes well beyond that by spelling out the exact response contract (tasks/returned/limit/truncated) and the meaning of the truncated flag plus the remediation path. This is meaningful behavioral disclosure the annotations cannot provide.

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 purpose, then return shape, then an Args block — the ordering is agent-friendly and each sentence carries information. Minor duplication of the 'limit' concept between the return-shape line and the Args block, and the Args-style formatting is slightly verbose for three parameters.

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

Completeness5/5

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

No output schema exists, and the description supplies the return shape and truncation semantics itself, so an agent has everything needed to call the tool and interpret its result. Filter values, defaults, and target resolution are all covered.

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

Parameters5/5

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

Schema coverage is 0% and the schema has no enum or descriptions, so the description fully compensates: it defines status's valid values (pending/success/failure), explains that limit is applied after filtering with default 200, and clarifies that target comes from config and may be omitted for the default.

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

Purpose5/5

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

States a specific verb and resource ('List XO tasks') plus the optional filter dimension ('by status'), and the [READ] tag signals the operation class. No sibling tool (backup_job_list, backup_log_list, snapshot_list, etc.) covers tasks, so the scope is unambiguous.

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

Usage Guidelines4/5

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

Gives concrete follow-up guidance for the truncated case ('re-run with a higher limit or a narrower status filter'), which tells the agent how to act on the result. It does not, however, state when this tool should be preferred over other listing tools or any preconditions, so it stops short of full when/when-not guidance.

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