Skip to main content
Glama
Sign In
vmware-mcp

vmware-mcp

by havu0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read Guest File

guest_read_file

Read a file from a guest VM by copying it to the host, retrieving its contents, and removing the temporary copy. Get file contents from any VMware virtual machine without manual steps.

Instructions

Read the contents of a file inside the guest VM. Copies to host, reads, then cleans up.

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_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmNoVM name or .vmx path
guest_pathYesFile path in guest to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden of revealing behavior. It explicitly discloses the temporary-copy workflow and cleanup ('Copies to host, reads, then cleans up'), which is valuable non-obvious context beyond just 'read file.' It does not mention failure cleanup or return behavior, but the core mutation/side-effect profile is clear.

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 one focused sentence that front-loads the operation and then concisely explains the temporary copy lifecycle. Every phrase earns its place.

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 two-parameter read operation, the description covers purpose and mechanism. However, without an output schema it does not explicitly state the return value (file contents) or error/edge-case behavior, so an agent must infer the output from the tool name and verb.

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%, and the parameter descriptions already define 'vm' and 'guest_path' adequately. The description adds no parameter-specific detail, so the baseline score applies.

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 ('Read') and resource ('a file inside the guest VM'), and its mechanism — 'Copies to host, reads, then cleans up' — sets it apart from sibling operations like file_copy_from_guest or guest_file_exists. The intent is unambiguous even without opening the schema.

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?

There is no guidance about when to choose this over alternatives, such as file_copy_from_guest for a persistent copy or guest_file_exists for existence checks. The description states what the tool does but provides no selection context.

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