Skip to main content
Glama

pve_node_startall

Start all or filtered virtual machines and containers on a Proxmox VE node. Use dry-run to plan before confirming execution.

Instructions

MUTATION: start all (or filtered) guests on a PVE node.

RISK_MEDIUM. Reversible — the inverse of pve_node_stopall. For a single guest instead of the whole node use pve_guest_power. vms = optional CSV of VMIDs to filter the scope. Dry-run by default (returns a PLAN); confirm=True executes (POST, Smoke-confirm on the vms param format) and returns {"status": "submitted", "result": <task UPID | None>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vmsNoOptional comma-separated list of VMIDs/CTIDs to limit the scope; omit to start all guests on the node.
nodeNoPVE node name whose guests to start; defaults to the configured node if omitted.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the bulk start.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided; description fully compensates by labeling as MUTATION, stating RISK_MEDIUM, reversibility, dry-run default, and providing return format details for both dry-run and execution modes.

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?

Concise and well-structured: front-loaded with key info (mutation, risk, sibling), then parameter details and return types. Every sentence adds value.

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

Completeness5/5

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

Despite no output schema shown, the description explains return types for both dry-run and execution. Covers all behavioral aspects and parameter roles adequately for the tool's complexity.

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?

Schema coverage is 100%, so baseline 3. The description adds some context (vms format as CSV, confirm behavior) but does not significantly enhance understanding beyond the schema descriptions.

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 tool starts all or filtered guests on a PVE node, distinguishing from sibling pve_guest_power (single guest) and pve_node_stopall (inverse).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidelines: 'For a single guest instead of the whole node use pve_guest_power.' Also explains dry-run vs confirm behavior and the inverse operation, making alternatives clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server