Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

set_container_root_password

Reset or set a running container's root password to a value the user types in Proxmox Controller, for lost credentials or password rotation; the assistant never sees it.

Instructions

Set a running container's root password to one the USER types in Proxmox Controller's window (you never give or see it) — for a container whose root password is lost, or to give it a new one. It runs pct exec -- chpasswd on the host over the app's SSH key, so it is a host command; the container must be on the node the app connects to.

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>",
      "vmid": "<vmid>",
      "reason": "<reason>"
    },
    "name": "set_container_root_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
vmidYesThe guest's ID (VMID).
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

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses the mechanism (pct exec <vmid> -- chpasswd over the app's SSH key), that this is a host command, that the secret is user-entered and never visible to the agent, and the placement constraint on the container. That is meaningful context the annotations do not convey.

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?

The purpose is front-loaded in the first clause, and the remaining details (password visibility, mechanism, placement constraint) are each load-bearing. The em-dash and semicolon construction makes it dense but not wasteful.

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 three-parameter mutation with no output schema, the description covers prerequisites, mechanism, and secret handling well. It does not say what a successful call returns or what happens if the container is stopped or on another node, leaving a small gap.

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 description coverage is 100%, with host, vmid, and reason all documented in the schema, so the baseline is 3. The description adds only that vmid feeds the pct exec command and implies host scoping; it adds no new meaning for the reason field or value formats.

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 states a specific verb and resource (set a running container's root password) and immediately distinguishes this from an agent-supplied secret by noting the USER types the password in the Proxmox Controller window and the agent never sees it. That detail separates it from a generic console-input tool like console_type_password.

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

Usage Guidelines4/5

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

It gives explicit when-to-use conditions: a container whose root password is lost, or one that needs a new password, plus prerequisites (container must be running and on the node the app connects to). It does not name an alternative tool or state when not to use it, so it stops short of a 5.

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