vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Run Command in Guest

guest_run_command

Execute shell commands in a VMware guest VM and retrieve stdout output. Select the shell automatically or specify cmd, PowerShell, bash, or sh, with optional timeout.

Instructions

Execute a shell command inside the guest VM and return stdout. Uses the appropriate shell based on guest OS type (cmd/bash). Requires guest credentials in config and VMware Tools running in guest.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "guest_run_command"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	No	VM name or .vmx path
`shell`	No	Shell to use. "auto" picks based on os_type	auto
`command`	Yes	Shell command to execute
`timeout_seconds`	No	Max execution time in seconds (vmrun hard limit is 300s)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It does disclose the stdout return, automatic shell selection, and VMware Tools requirement, but it leaves unstated how failures are reported, whether stderr/exit codes are included, and the fact that arbitrary shell commands can modify guest state.

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 concise sentences with no filler. The main behavior is front-loaded, and the second sentence adds only necessary environmental and shell-selection details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the schema fully documents all parameters and the description covers prerequisites, output (stdout), and shell behavior, the tool is mostly complete to invoke correctly. The main missing context is failure/exit-code semantics and explicit differentiation from guest_run_program, but these are not critical for basic invocation.

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 already covers all parameters at 100%, so the baseline is 3. The description adds value beyond the schema by clarifying that 'command' is a shell command rather than a program path and that the shell auto-selects based on guest OS type, which reinforces the 'shell' parameter behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Execute a shell command inside the guest VM and return stdout.' It names a specific verb, resource, and expected output. The 'shell command' phrasing also helps distinguish it from the sibling guest_run_program.

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 description gives useful prerequisites and context: guest credentials must be configured and VMware Tools must be running, and shell selection depends on guest OS. However, it does not explicitly explain when to use this tool over guest_run_program or provide exclusions or alternative routing.

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