Skip to main content
Glama
vmware-skills

VMware-Monitor

by vmware-skills
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_virtual_machines

Read-onlyIdempotent

List VMware virtual machines with filtering by power state or folder, sorting, and selectable fields to quickly resolve a VM name for further investigation.

Instructions

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

Returns the family list envelope {items, returned, limit, total, truncated, hint}; total is the real post-filter count, so read truncated before summarising. Over 50 VMs with no limit/fields, only the first five fields below come back (mode says which). vms is a deprecated pre-1.8.0 alias of items, removed in 2.0 — read items.

Use this to resolve an exact VM name, then vm_info for detail or vm_investigation_bundle to drill into one; for a fleet-wide view start at cluster_health_summary instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax VMs (None = all).
fieldsNoAny of name, power_state, cpu, memory_mb, folder_path, guest_os, ip_address, host, uuid, tools_status (None = auto).
targetNovCenter/ESXi target from config (default if omitted).
sort_byNoname | cpu | memory_mb | power_state | folder_path.name
power_stateNopoweredOn | poweredOff | suspended.
folder_filterNoCase-insensitive folder_path substring; nested folders match.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / fields / description
      Added value: +"Any of name, power_state, cpu, memory_mb, folder_path, guest_os, ip_address, host, uuid, tools_status (None = auto)."
    • addedInput schema / properties / folder_filter / description
      Added value: +"Case-insensitive folder_path substring; nested folders match."
    • addedInput schema / properties / limit / description
      Added value: +"Max VMs (None = all)."
    • addedInput schema / properties / power_state / description
      Added value: +"poweredOn | poweredOff | suspended."
    • addedInput schema / properties / sort_by / description
      Added value: +"name | cpu | memory_mb | power_state | folder_path."
    • addedInput schema / properties / target / description
      Added value: +"vCenter/ESXi target from config (default if omitted)."
  2. Changed1 schema field changedv1.5.22
    • addedInput schema / properties / folder_filter
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Folder Filter"
+}
  3. Changed5 schema fields changedv1.5.18
    • addedInput schema / properties / fields
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Fields"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Limit"
+}
    • addedInput schema / properties / power_state
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Power State"
+}
    • addedInput schema / properties / sort_by
      Added value: +{
+  "default": "name",
+  "title": "Sort By",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_virtual_machinesOutput",
-  "type": "object"
-}New value: +null
  4. First observedv0.1.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's job is to add runtime behavior. It does so in detail: the response envelope, the meaning of 'total' vs 'truncated', the 50-VM default-field truncation, and the deprecated 'vms' alias. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: purpose, response semantics, truncation caveat, deprecation note, and usage routing. It is front-loaded with the core operation and uses code formatting to isolate field names. No filler or 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?

Given there is no output schema, the description fully carries return-value explanation: envelope fields, truncation semantics, and the deprecated alias. It also contextualizes the operation among siblings. For a read-only list tool with six optional parameters, nothing critical is missing for an agent to call and interpret it correctly.

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 100%, so the baseline is 3. The description adds genuine extra semantics beyond the schema by explaining how 'limit' and 'fields' interact under the 50-VM threshold and introducing the 'mode' field as an indicator of which fields were returned. This goes beyond simply restating parameter names.

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 opening sentence states an explicit verb and resource: 'List virtual machines, with filtering, sorting, and field selection.' It further distinguishes itself by steering agents to use this for resolving an exact VM name, versus vm_info, vm_investigation_bundle, or cluster_health_summary for other needs.

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

Usage Guidelines5/5

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

The final paragraph gives explicit routing guidance: use this tool to resolve an exact VM name, then delegate to vm_info for detail or vm_investigation_bundle for deeper investigation, and use cluster_health_summary for a fleet-wide view. This clearly tells the agent when this tool is the right choice and when a sibling is preferable.

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/vmware-skills/VMware-Monitor'

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