Skip to main content
Glama

vsphere_start_vm

Power on a vSphere virtual machine by name, optionally through a specified gateway, to restore workloads after shutdown or maintenance.

Instructions

Power on a vSphere VM.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing beyond the action itself. It does not say whether the call blocks until the VM is powered on, what happens if the VM is already running, whether the operation is idempotent, or what permissions/credentials 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, which is structurally sound. However, its brevity comes from under-specification rather than efficiency, leaving no room for the operational context an agent needs.

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

Completeness1/5

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

For a mutation tool with no annotations, no output schema, and zero schema description coverage, the description supplies essentially nothing beyond the action. An agent could not determine required state, identifier format, gateway semantics, or return behavior from this definition.

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 both parameters are undocumented, and the description does not compensate. It never clarifies whether `name` is a VM display name, inventory path, or UUID, nor does it explain what `gateway_id` selects or when it should be supplied.

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 ("Power on a vSphere VM"), which is unambiguous and clearly separable from vsphere_stop_vm and vsphere_restart_vm by the verb alone. It does not explicitly name or route against those siblings, so it stops short of a 5.

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 on when to use this versus vsphere_restart_vm or vsphere_migrate_vm, nor on prerequisites such as the VM needing to be powered off first. The agent must infer all usage conditions from the tool name and its own knowledge of vSphere.

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