Skip to main content
Glama
Sign In
AIops-tools

xcpng-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vm_stats

Read-only

Retrieve recent RRD-backed CPU and memory averages for a specified VM, with optional time granularity, to monitor performance and diagnose issues.

Instructions

[READ] Recent CPU / memory stats for a VM (RRD-backed averages).

Args:
    vm_id: VM uuid (see vm_list).
    granularity: seconds / minutes / hours / days (default seconds).
    target: Xen Orchestra target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
vm_idYes
targetNo
granularityNoseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already declares the safe-read profile, and '[READ]' merely restates it. The description does add useful context beyond annotations: these are RRD-backed *averages* (aggregation semantics) and the granularity determines resolution. It still says nothing about latency, caching, or result shape.

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 purpose and a clear READ tag, then an Args block covering each parameter. Efficient and well-organized, with only minor redundancy between '[READ]' and the readOnlyHint annotation.

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?

No output schema exists, yet the description never characterizes the returned stats (metric names, units, time-window shape). For a simple read tool with all params documented this is adequate but leaves the return value opaque.

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?

Schema coverage is 0%, so the description carries the burden and does so for all three parameters: vm_id as a VM uuid with a pointer to vm_list, granularity's value set (seconds/minutes/hours/days) and default, and target's meaning with the omit-for-default rule. The granularity value list is especially valuable since the schema has no enum.

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 resource (VM) and content (CPU/memory stats), further qualified as RRD-backed averages. This distinguishes it reasonably well from vm_get (full details) and vm_health_rca (health diagnosis), though it never names a sibling 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 guidance on when to prefer this tool over vm_get, vm_health_rca, or vm_list. The '(see vm_list)' note is a cross-reference for obtaining a vm_id, not usage guidance, and no exclusions or prerequisites are given.

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