vmware-mcp

Overview Schema Source Related Servers Discussions Admin

List VMs

vm_list

List virtual machines to check running status, or include all configured VMs to view their running state for complete inventory.

Instructions

List virtual machines. By default shows only running VMs. Use all=true to include configured VMs from config.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vm_list"
  }
}

Input Schema

Name	Required	Description	Default
`all`	No	Include all configured VMs with their running status

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly discloses the default filtering behavior and the effect of all=true, which is meaningful beyond the schema. It does not mention potential errors or permissions, but for a read-only listing operation the key behavior is covered.

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 two short sentences with no filler. The primary action comes first, followed by the important default behavior and the parameter action. Every word earns its place.

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?

For a tool with one optional boolean parameter and no output schema, the description covers what the agent needs to invoke it correctly: the default behavior and when to set all=true. It does not describe the return format in detail, but 'List virtual machines' makes the high-level output clear.

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 value by explaining the default outcome ('By default shows only running VMs') and by linking all=true to 'configured VMs from config', which clarifies the practical meaning of the parameter beyond its schema description.

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 opens with a specific verb and resource ('List virtual machines') and immediately distinguishes itself from the many sibling tools by scoping behavior: default is running VMs only, with an option for configured VMs. There is no ambiguity about what this tool does.

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?

It gives clear usage context: by default you get running VMs, and you should pass all=true if you want configured VMs from config. It does not explicitly name alternatives or when-not-to-use, but the guidance is sufficient for a simple listing tool with one optional boolean parameter.

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