vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Run Program in Guest

guest_run_program

Run a program inside a VMware guest VM by providing its full path, with optional arguments and timeout. Use no_wait to launch it asynchronously and return immediately.

Instructions

Launch a program inside the guest VM. Can run asynchronously with no_wait. Requires full path to the program.

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": {
      "program": "<program>"
    },
    "name": "guest_run_program"
  }
}

Input Schema

Name	Required	Description
`vm`	No	VM name or .vmx path
`args`	No	Program arguments
`no_wait`	No	Return immediately without waiting for the program to finish
`program`	Yes	Full path to the program in the guest
`timeout_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds only that the launch can be asynchronous and that a full path is required, both of which are already present in the schema. It does not describe return behavior, stdout/stderr, default waiting behavior, or failure semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with the primary action front-loaded and no filler. It is efficient, though its brevity leaves important behavioral and selection details uncovered.

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

Completeness2/5

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

For a tool with five parameters, no output schema, and no annotations, this description is too thin. It leaves timeout_seconds undocumented, does not describe expected return behavior, and does not explain when to prefer this over guest_run_command.

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 80%, so the baseline is 3. The description repeats the full-path requirement for program but does not add meaning for timeout_seconds, argument passing, or how no_wait interacts with the overall execution.

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?

States a specific action and object: 'Launch a program inside the guest VM' and adds the requirement of a full path. It is clear about the resource, but does not explicitly differentiate from the sibling guest_run_command, so it stops short of 5.

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?

Provides no when-to-use guidance, exclusions, or alternatives. The mention of no_wait and full path is a capability note, not selection guidance, and the close sibling guest_run_command could easily be chosen instead.

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