vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Copy File to Guest

file_copy_to_guest

Copy files from the host to a virtual machine's guest OS. Transfer a local file to a specified destination path inside the VM.

Instructions

Copy a file from the host machine to the guest VM.

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": {
      "host_path": "<host_path>",
      "guest_path": "<guest_path>"
    },
    "name": "file_copy_to_guest"
  }
}

Input Schema

Name	Required	Description
`vm`	No	VM name or .vmx path
`host_path`	Yes	Source file path on host
`guest_path`	Yes	Destination file path in guest

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are present, so the description carries the full behavioral burden. It only states the basic copy action and does not disclose whether existing files are overwritten, whether the VM must be running or have guest tools installed, or what happens on failure.

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 direction, and every word contributes to understanding the tool's purpose.

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 three-parameter operation, the description and schema provide enough to attempt a call, but important contextual details are missing: overwrite behavior, guest-side prerequisites, and whether the operation returns any result. The absence of annotations makes these gaps more significant.

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 input schema already documents all three parameters clearly. The description reinforces the host-to-guest direction but adds no parameter-level meaning beyond what the schema properties already provide.

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 states a specific verb ('Copy'), a specific resource ('a file'), and an unambiguous direction ('from the host machine to the guest VM'). This clearly distinguishes it from the sibling tool file_copy_from_guest, which moves in the opposite direction.

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

Usage Guidelines4/5

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

The description makes the core usage context clear: this is the tool to use when transferring a file from host to guest. It does not explicitly name alternatives or state when not to use it, but the directionality itself is strong contextual guidance.

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