Check the current status of a Parallels Desktop virtual machine by providing its name or UUID, so you can see whether it is running, stopped, or suspended.
Get the current status of a virtual machine
| Name | Required | Description | Default |
|---|---|---|---|
| vm | Yes | VM name or UUID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It says nothing about whether this is a safe read (implied but unstated), what 'status' values exist, whether the VM must be powered on, latency, or error behavior for unknown VMs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with the resource and scope front-loaded and no filler. It is terse to the point of being under-specified, but not verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter read with no annotations and no output schema, the description is minimally adequate. It never conveys what the returned status looks like (running/stopped/suspended), which is the tool's whole purpose and is not covered by any structured field.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and there is a single parameter ('vm') documented as 'VM name or UUID'. The description adds no meaning beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('current status of a virtual machine'), so the agent knows exactly what it retrieves. However, it does not differentiate itself from the close sibling get_vm_info, which an agent could easily confuse with a status query.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance and no alternatives named, despite eight siblings including get_vm_info, list_vms, and the start/stop/suspend lifecycle tools. The agent must infer from the name alone that this is the status-only read.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.