vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Create Temp File in Guest

guest_create_tempfile

Creates a temporary file in a VMware guest VM and returns its path. Use to obtain a writable temp location for scripts or data.

Instructions

Create a temporary file inside the guest VM and return its path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "guest_create_tempfile"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	No	VM name or .vmx path

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?

There are no annotations, so the description carries the full burden of behavioral disclosure. It states that a temporary file is created and its path returned, but it does not explain lifecycle, whether the file persists after VM operations, whether guest tools are required, or what failure modes exist. For a mutating operation this is a notable gap.

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?

The description is a single sentence with no filler and front-loads the core action. It communicates purpose and result efficiently, though it omits some useful behavioral 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?

For a one-parameter tool this is minimal but functional: it tells what happens and what is returned. However, with no annotations, no output schema, and no usage guidance, the description leaves uncertainty about temporary-file lifecycle and operational prerequisites, so it is only marginally 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?

The input schema has 100% description coverage for its single parameter ('VM name or .vmx path'). The description adds no additional parameter semantics, so the baseline of 3 is appropriate because the schema already documents the parameter adequately.

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?

The description states a clear verb ('Create'), a specific resource ('a temporary file inside the guest VM'), and the result ('return its path'). It is not a tautology and is distinguishable from sibling file tools by emphasizing temporary file creation, though it does not explicitly name or contrast with sibling tools.

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 is provided about when to use this tool versus alternatives like file_copy_to_guest, guest_read_file, or guest_directory_create. The agent is left to infer the appropriate context from the name and description alone.

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