vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Reset VM

vm_reset

Reset (reboot) a VMware virtual machine. Use soft mode to run guest shutdown scripts before restarting, or hard mode for an immediate power reset.

Instructions

Reset (reboot) a virtual machine. "soft" runs shutdown scripts first.

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

Input Schema

Name	Required	Description	Default
`vm`	No	VM name from config, or full .vmx path. Uses default_vm if omitted
`mode`	No		soft

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one meaningful behavioral trait: 'soft' runs shutdown scripts first, implying 'hard' does not. However, it does not mention potential data loss, abruptness of hard reset, or any prerequisites like guest tools.

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?

Two compact sentences with the core action front-loaded and the mode detail second. No filler or redundant phrasing.

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?

For a simple 2-optional-parameter tool with no annotations and no output schema, the description covers the essential action and one mode behavior. Gaps remain around hard-mode semantics and side effects, but the description is sufficient for basic invocation.

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 schema already documents 'vm' well, but 'mode' only has an enum with no description. The description compensates partially by explaining what 'soft' does, though it leaves 'hard' undefined. Since schema description coverage is 50%, the additional mode context helps but is incomplete.

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 'Reset (reboot) a virtual machine,' which is a specific verb and resource. The parenthetical 'reboot' helps distinguish it from stop/start operations, though it does not explicitly name or differentiate from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mention of 'soft' running shutdown scripts first implies a graceful vs. forced reset, giving some context for choosing a mode. However, there is no explicit guidance on when to use this tool versus alternatives like vm_stop or vm_start, nor any exclusions.

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