Skip to main content
Glama
Sign In
vmware-mcp

vmware-mcp

by havu0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pause VM

vm_pause

Pause a running virtual machine to suspend its activity without shutting down. Retains the current state so you can resume later exactly where you left off.

Instructions

Pause a running virtual machine without shutting it down.

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_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmNoVM name from config, or full .vmx path. Uses default_vm if omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clarifis that the operation is not a shutdown, but it does not explain what pausing does (e.g., freezes execution, keeps memory state), whether it is reversible, or what errors or side effects may occur.

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 with no filler. It front-loads the action and adds one useful qualifier, making it well structured for a tool with only one optional parameter.

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?

The tool is simple and the schema covers its lone parameter, so the description does not need much. However, without annotations or an output schema, it lacks guidance on how to resume a paused VM and what state the VM enters, leaving some ambiguity for an agent.

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?

Schema description coverage is 100%, so the baseline applies. The description itself adds no parameter details, but the schema already documents that vm accepts a name or .vmx path and defaults to default_vm.

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 states a clear verb and resource: pause a virtual machine. The phrase 'without shutting it down' distinguishes it from vm_stop, but it does not differentiate it from thge similarly named sibling vm_suspend, so it does not fully disambiguate among siblings.

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?

There is no explicit guidance about when to use vm_pause versus the closely related siblings vm_suspend, vm_stop, or vm_unpause. The only implication is that the VM must be running, but no althernative selection criteria are provided.

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

Deploy Server

Other Tools