Skip to main content
Glama
Sign In
vmware-mcp

vmware-mcp

by havu0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check VMware Tools

vm_check_tools

Check the VMware Tools state in a VM to determine if the guest is unknown, installed, or running, confirming integration status.

Instructions

Check the VMware Tools state in the guest. Returns "unknown", "installed", or "running".

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": "vm_check_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmNoVM name or .vmx path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the possible return values, which is helpful, but does not explain the meaning of each state, error conditions, or whether the operation is read-only. Since the tool is a simple check, the impact is limited, but more context would be beneficial.

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, dense sentence that front-loads the action and immediately specifies the output values. Every word earns its place, with no unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple state-check tool with one parameter and no output schema, the description is mostly complete. It lists the possible return values, which is essential since there is no output schema. However, it does not explain the conditions that lead to each state or mention error scenarios, which would help an agent handle unexpected situations.

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 only parameter, 'vm', is already fully described in the schema as 'VM name or .vmx path'. The tool description adds no additional meaning to the parameter, so the baseline of 3 applies due to 100% schema coverage.

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 clearly states the action ('Check'), the resource ('VMware Tools state in the guest'), and the expected return values ('unknown', 'installed', or 'running'). This distinguishes it from sibling tools like vm_status (VM power state) and vm_get_ip (network address).

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 gives no explicit guidance on when to use this tool versus alternatives. The purpose makes it obvious it should be used to check guest tools status, likely before executing guest operations, but this is only implied and not stated.

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