Skip to main content
Glama
Sign In
vmware-mcp

vmware-mcp

by havu0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Copy File from Guest

file_copy_from_guest

Copy a file from a virtual machine to the host machine by specifying the guest source path and a destination path on the host.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
vmNoVM name or .vmx path
host_pathYesDestination file path on host
guest_pathYesSource file path in guest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 behavioral disclosure burden. It states the basic copy action but does not reveal whether the host destination is overwritten, whether directories are supported, or whether VMware Tools must be running.

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?

One sentence, front-loaded with the core action, and every word contributes. There is no filler, redundancy, or unnecessary detail.

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 description is minimally adequate for a simple copy operation: it identifies the source, destination, and direction, and the schema covers the parameters. However, with no annotations and no output schema, useful context such as overwrite behavior and VMware Tools prerequisites is missing.

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. The description adds no parameter-specific detail beyond the schema, matching the baseline of 3.

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 uses a specific verb ('Copy') with a clear source and destination: from the guest VM to the host machine. It unambiguously distinguishes this tool from file_copy_to_guest, which performs the reverse transfer.

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 implies when to use the tool: when a file needs to be transferred from the guest to the host. However, it does not explicitly discuss alternatives or exclusions, such as using guest_read_file for reading content instead of copying a file.

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