vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Create Guest Directory

guest_directory_create

Creates a specified directory path inside a guest virtual machine. Use to prepare folders for file transfers or application installation.

Instructions

Create a directory 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_directory_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations are absent, so the description must carry the behavioral burden. It only states that a directory is created; it does not disclose behavior when the directory already exists, whether parent directories are created, or other side effects.

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?

Single sentence with no filler; it front-loads the action and object. The description is appropriately sized for a simple tool definition, even though other dimensions lack depth.

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 two-parameter creation tool, the schema plus description provide a usable baseline for invocation. However, missing behavior around existing paths and the optional vm default leaves non-trivial gaps for an agent deciding how to call it correctly.

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 well documented. The description adds little beyond the schema; 'inside the guest VM' essentially restates the guest_path schema description.

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 verb ('Create') and resource ('directory') with a clear location ('inside the guest VM'). This distinguishes it from file copy/delete/rename operations, though it does not explicitly name sibling alternatives.

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?

No guidance on when to use this tool versus alternatives such as guest_directory_exists or guest_list_directory. There is no mention of prerequisites, whether the VM must be running, or when this should be preferred over file operations.

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