Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

wake_host

Powers on a Proxmox host through Wake-on-LAN when it supports and is configured for it, using the host ID and a required reason for approval.

Instructions

Turn the host on with Wake-on-LAN (it must support it and be set up for it).

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": {
      "host": "<host>",
      "reason": "<reason>"
    },
    "name": "wake_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already state this is a non-readOnly, non-destructive, non-idempotent operation, so the safety profile is covered. The description adds genuinely useful operational context those annotations lack: the WoL capability and configuration requirement, which determines whether the call can succeed at all. It could go further by noting boot latency or the failure behavior, but the added constraint is substantive.

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 the action first and the constraint second; nothing is redundant. It is lean to the point of being slightly terse, but every clause carries information.

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

Completeness4/5

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

For a two-parameter, annotation-covered, output-schema-less tool, the description supplies purpose, mechanism, and the key precondition, which is close to sufficient. Minor gaps remain around timing expectations and behavior when WoL is unavailable.

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% and both parameters are well documented in the schema, including that host ids come from list_hosts and that reason is shown in the approval window. The description adds no parameter detail beyond that, so baseline 3 applies.

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?

Names a specific verb and resource ('Turn the host on') plus the mechanism (Wake-on-LAN), which separates it from guest-level siblings like guest_power and from generic host tools like host_power. It does not explicitly name an alternative, but the host-vs-guest and WoL-specific scope is unambiguous.

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 parenthetical gives a real precondition (host must support WoL and be configured for it), which is the main 'when it will work' guidance. It stops short of routing guidance: no mention of what to use instead if WoL is unsupported, or whether this only applies to a powered-off host.

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