Skip to main content
Glama
yeahdongcn

VMware Fusion MCP Server

by yeahdongcn

get_vm_info

Retrieve detailed information about a specific VMware Fusion virtual machine, including configuration and status, by providing its VM ID.

Instructions

Get detailed information about a specific VM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vm_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary MCP tool handler for 'get_vm_info', registered via @mcp.tool decorator. It delegates to the internal implementation.
    @mcp.tool
    async def get_vm_info(vm_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific VM."""
        return await _get_vm_info_impl(vm_id)
  • Internal helper function that instantiates VMwareClient and calls its get_vm_info method to fetch VM details.
    async def _get_vm_info_impl(vm_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific VM."""
        async with VMwareClient(username=VMREST_USER, password=VMREST_PASS) as client:
            info = await client.get_vm_info(vm_id)
            return info  # type: ignore[no-any-return]
  • Core implementation in VMwareClient that makes HTTP GET request to VMware Fusion REST API endpoint `/api/vms/{vm_id}` to retrieve VM information.
    async def get_vm_info(
        self, vm_id: str, vm_password: Optional[str] = None
    ) -> Dict[str, Any]:
        """Get detailed information about a specific VM.
    
        Args:
            vm_id: The ID of the VM
            vm_password: The password for the VM (if required)
    
        Returns:
            Dictionary with detailed VM information
        """
        try:
            url = f"{self.base_url}/api/vms/{vm_id}"
            params = {}
            if vm_password:
                params["vmPassword"] = vm_password
            response = await self._client.get(
                url,
                headers=self._auth_header,
                params=params or None,
            )
            response.raise_for_status()
            result: 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:
            if e.response.status_code == 404:
                raise Exception(f"VM with ID '{vm_id}' not found")
            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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool gets 'detailed information' but doesn't specify what that includes (e.g., configuration, status, metadata), whether it's read-only, or any prerequisites like authentication. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 fluff. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is somewhat complete. However, with no annotations and minimal parameter guidance, it lacks details on behavioral traits and usage context, making it adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description adds minimal context by implying 'vm_id' identifies a specific VM, but doesn't explain what format the ID should be (e.g., UUID, name) or where to find it. This partially compensates for the schema gap but remains vague.

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 ('Get') and resource ('detailed information about a specific VM'), making the purpose unambiguous. It distinguishes from siblings like 'list_vms' (which lists multiple VMs) and 'power_vm' (which controls power state), though it doesn't explicitly mention 'get_vm_power_state' which might overlap in scope.

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. It doesn't mention that 'list_vms' might be better for discovering VMs, or that 'get_vm_power_state' might be sufficient if only power state is needed. The description implies usage for a specific VM but offers no exclusions or 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/yeahdongcn/vmware-fusion-mcp-server'

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