Skip to main content
Glama
zw008

VMware-Monitor

list_virtual_machines

Read-onlyIdempotent

List VMware virtual machines with filtering by power state, folder path, and custom fields. Sort results and limit output for efficient inventory management.

Instructions

[READ] List virtual machines with optional filtering, sorting, and field selection.

Returns a dict: {total, mode, vms, hint}. Each VM entry includes a folder_path field showing the vCenter inventory folder path (e.g. /Colocation/Colo - ISER).

Auto-compact: when no limit/fields are set and inventory exceeds 50 VMs, returns compact fields (name, power_state, cpu, memory_mb, folder_path) to keep context manageable. Set limit or fields to override.

Args: target: Optional vCenter/ESXi target name from config. Uses default if omitted. limit: Max number of VMs to return (None = all). sort_by: Sort field: "name" | "cpu" | "memory_mb" | "power_state" | "folder_path". power_state: Filter by power state: "poweredOn" | "poweredOff" | "suspended". fields: Return only these fields (None = auto-select based on inventory size). Available: name, power_state, cpu, memory_mb, guest_os, ip_address, host, uuid, tools_status, folder_path. folder_filter: Case-insensitive substring match against folder_path. Example: folder_filter="Colocation" returns VMs anywhere under a Colocation folder, including nested subfolders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
fieldsNo
targetNo
sort_byNoname
power_stateNo
folder_filterNo
Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description goes beyond by revealing auto-compact logic (when no limit/fields and inventory > 50 VMs, returns compact fields) and the folder_path field. No contradiction 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?

The description is front-loaded with purpose and structured with sections. The parameter list is thorough but slightly lengthy. Overall efficient with minimal redundancy.

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, but the description explains the return dict structure ({total, mode, vms, hint}) and key field folder_path. All 6 parameters are explained with types, defaults, and behavior. Example given for folder_filter. Complete for a read-only list tool.

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 description coverage is 0%, but the description provides full parameter documentation: target (optional), limit (max VMs), sort_by (enum values), power_state (filter), fields (available options), folder_filter (case-insensitive substring match). This adds significant meaning beyond the raw schema.

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?

The description starts with '[READ] List virtual machines with optional filtering, sorting, and field selection.' It clearly states the verb 'list' and the resource 'virtual machines,' and distinguishes from siblings like vm_info (for a single VM) and other list tools.

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?

The description explains when to use (listing VMs with filters) and details auto-compact behavior that guides usage when no limit/fields are set. It does not explicitly compare to alternatives or state when not to use, but the context is clear enough.

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