Skip to main content
Glama

vsphere_stop_vm

Shut down a vSphere VM gracefully via VMware Tools, or set force=True for an immediate hard power-off.

Instructions

Shut down a vSphere VM. Attempts guest shutdown via VMware Tools by default; set force=True for immediate hard power-off.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
forceNo
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the default graceful guest shutdown and the hard power-off behavior of force=True, but it omits the disruptive/destructive nature of hard power-off, permission requirements, idempotency, and what happens if VMware Tools is unavailable.

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 two concise sentences with the primary purpose front-loaded and the force behavior explained without unnecessary wording.

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

Completeness2/5

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

For a disruptive VM operation with no annotations, no output schema, and 0% schema description coverage across three parameters, the description is incomplete. It explains the graceful/hard shutdown distinction but leaves gateway_id undocumented and does not warn about potential data loss or prerequisites.

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%, so the description must compensate. It explains force=True well, but it does not clarify the required name parameter or the gateway_id parameter at all.

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 specific verb and resource: "Shut down a vSphere VM." It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools such as vsphere_restart_vm or vsphere_start_vm.

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?

It gives useful guidance on choosing graceful shutdown versus force=True hard power-off via VMware Tools, but does not say when to use this tool versus restart/start alternatives, nor does it mention prerequisites such as the VM being powered on or VMware Tools availability.

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