vmware-mcp

by havu0

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Delete Guest File

guest_delete_file

Deletes a specified file in a VMware guest OS using vmrun, solving file removal without manual guest login.

Instructions

Delete a file inside 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": {
      "guest_path": "<guest_path>"
    },
    "name": "guest_delete_file"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	No	VM name or .vmx path
`guest_path`	Yes	File path to delete in guest

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits itself. It only states that a file is deleted, without noting that deletion is permanent, that it may fail if the path is a directory, or that it requires guest cooperation. This is a meaningful gap for a destructive operation.

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 clear sentence with no filler. It is front-loaded with the action and resource, making it easy to scan and process.

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?

While the tool is simple, the description omits important context for correct invocation and expectation-setting: no mention of reversibility, failure conditions, or runtime requirements. For a destructive guest operation with no annotations, this is insufficiently complete.

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 parameters are already fully documented in the schema. The tool description adds no extra parameter meaning, but the baseline of 3 applies because the schema carries the informational burden.

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 ('Delete') and resource ('a file inside the guest VM'), which clearly distinguishes it from sibling tools like guest_read_file, guest_rename_file, or file_copy_to_guest. The scope is explicit and unambiguous.

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?

The description gives no guidance on when to use this tool versus alternatives such as guest_run_command with rm, or how to handle cases like deleting directories vs files. There is no mention of prerequisites like the VM being powered on or VMware Tools being installed.

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