Skip to main content
Glama

xo_start_vm

Start a halted XCP-ng VM by VM ID to bring stopped workloads back online through the vibops-mcp control plane.

Instructions

Start a halted XCP-ng 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": {
      "vm_id": "<vm_id>"
    },
    "name": "xo_start_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
vm_idYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden and carries almost none of it: nothing about required permissions, behavior on an already-running VM, whether the call is asynchronous, or what side effects occur. Only the mutation intent is conveyed by the verb "Start".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is appropriately terse, though the terseness comes at the cost of the missing behavioral and parameter detail rather than being a model of efficient completeness.

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 write operation with zero annotation coverage, no output schema, and fully undocumented parameters, one sentence is not enough. An agent knows what the tool nominally does but not how to call it safely or what to expect in response.

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 and does not — neither vm_id nor the unexplained gateway_id is mentioned. The gateway_id parameter in particular has no schema description and no textual explanation of 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 gives a specific verb ("Start") plus the resource ("XCP-ng VM") and a state qualifier ("halted"), which is enough to distinguish it from xo_stop_vm or the proxmox/vsphere equivalents. It falls short of a 5 only because it never explicitly names or contrasts a sibling tool.

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 word "halted" implies the precondition for use, so an agent can infer this is for powered-off VMs. However, there is no statement of what to do when the VM is already running, no mention of alternatives, and no routing guidance despite many sibling start/stop/migrate tools.

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