Skip to main content
Glama
yeahdongcn

VMware Fusion MCP Server

by yeahdongcn

list_vms

Retrieve a list of all virtual machines in VMware Fusion to monitor and manage your virtualization environment.

Instructions

List all VMs in VMware Fusion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'list_vms', registered via @mcp.tool decorator. It calls the internal _list_vms_impl function to perform the listing.
    @mcp.tool
    async def list_vms() -> Dict[str, Any]:
        """List all VMs in VMware Fusion."""
        return await _list_vms_impl()
  • Helper function that creates a VMwareClient instance and calls list_vms() on it, wrapping the result in a dict.
    async def _list_vms_impl() -> Dict[str, Any]:
        """List all VMs in VMware Fusion."""
        async with VMwareClient(username=VMREST_USER, password=VMREST_PASS) as client:
            vms = await client.list_vms()
            return {"vms": vms}  # type: ignore[no-any-return]
  • Core implementation in VMwareClient that makes an HTTP GET request to /api/vms endpoint to fetch the list of VMs from Fusion REST API.
    async def list_vms(self) -> List[Dict[str, Any]]:
        """List all VMs.
    
        Returns:
            List of VM dictionaries with basic information
        """
        try:
            response = await self._client.get(
                f"{self.base_url}/api/vms",
                headers=self._auth_header,
            )
            response.raise_for_status()
            result: List[Dict[str, Any]] = response.json()
            return result
        except httpx.RequestError as e:
            raise Exception(f"Failed to connect to VMware Fusion API: {e}")
        except httpx.HTTPStatusError as e:
            raise Exception(
                f"VMware Fusion API error: {e.response.status_code} - "
                f"{e.response.text}"
            )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't describe what 'list' entails—e.g., whether it returns names, IDs, statuses, or pagination details. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and output.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple listing operation.

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?

Given the tool's simplicity (0 parameters, output schema exists), the description is minimally adequate. However, with no annotations and an output schema present, it doesn't explain what the listing includes or how to interpret results, leaving some context gaps despite the structured output.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are none. A baseline of 4 is applied for zero parameters, as no compensation is needed.

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?

The description clearly states the verb ('List') and resource ('all VMs in VMware Fusion'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like get_vm_info (which retrieves detailed info for a specific VM) or power_vm (which controls power state), but the basic action is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention that list_vms returns a broad overview while get_vm_info provides detailed data for a specific VM, or that it might be a prerequisite for operations like power_vm. Usage context is implied but not explicit.

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/yeahdongcn/vmware-fusion-mcp-server'

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