Skip to main content
Glama
zw008

VMware-Monitor

by zw008
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

vm_list_snapshots

Read-onlyIdempotent

List all snapshots of a virtual machine with their hierarchy, including name, description, creation timestamp, state, and nesting level. Read-only operation.

Instructions

[READ] List all snapshots of a VM, including the nesting hierarchy.

Returns one entry per snapshot with name, description, created timestamp, state, and level (0 = root; children are level+1). Returns an empty list when the VM has no snapshots. Read-only — this skill cannot create, revert, or delete snapshots (use vmware-aiops for those operations). Exposes the same data as the CLI command vmware-monitor vm snapshot-list (was missing from MCP until 2026-06-08 — CLI/MCP parity, 踩坑 #34).

Args: vm_name: Exact name of the virtual machine. target: Optional vCenter/ESXi target name from config. Uses default if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
vm_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Adds useful behavioral info (empty list for no snapshots) beyond annotations. No contradictions with annotations.

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?

Well-structured with [READ] tag and logical sections. Slight clutter from internal issue reference but overall efficient.

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?

Covers output format and parameter semantics adequately. With output schema present, return values are fully specified.

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?

Provides clear definitions for both parameters (exact name, optional target with default) where schema had only titles and types.

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?

Clearly states it lists snapshots of a VM with nesting hierarchy. Provides detailed output structure. Distinguishes from siblings as the only snapshot-specific tool.

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?

Explicitly notes read-only nature and directs mutating operations to vmware-aiops. Does not explicitly state 'use when listing snapshots' but that is clear from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zw008/vmware-monitor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server