Skip to main content
Glama

vsphere_restart_vm

Restarts a vSphere virtual machine via VMware Tools guest reboot by default, or set force=True for an immediate hard reset when the guest is unresponsive.

Instructions

Restart a vSphere VM. Attempts guest reboot via VMware Tools by default; set force=True for immediate hard reset.

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": {
      "name": "<name>"
    },
    "name": "vsphere_restart_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
forceNo
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the default graceful mechanism and the force alternative, but omits critical traits for a disruptive mutation: what happens if VMware Tools is absent, that a hard reset risks data loss or an unclean guest shutdown, and what permissions are required.

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?

Two short sentences with no waste, and the primary action is front-loaded ahead of the mode-switching detail. Every clause adds information an agent needs.

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 destructive operation with no annotations and no output schema, the description covers the core action and the force semantics but leaves gaps: gateway_id meaning, behavior on Tools-less guests, and failure/return expectations. Adequate to invoke, not complete enough to invoke safely in edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate. It does explain 'force' well (default guest reboot vs. immediate hard reset), but leaves 'name' and especially 'gateway_id' entirely unexplained, leaving two of three parameters undocumented in both schema and 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?

The description names a specific verb and resource ('Restart a vSphere VM'), which is unambiguous and clearly distinct from vsphere_start_vm, vsphere_stop_vm, and vsphere_get_vm. It does not explicitly name those siblings as alternatives, so it stops short of full sibling differentiation.

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?

Usage context is implied rather than stated: the default path (guest reboot via VMware Tools) versus force=True (hard reset) tells an agent the two modes exist. There is no explicit when-to-use/when-not-to-use guidance, no prerequisites, and no mention of when to prefer stop+start or another tool.

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