Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

list_hosts

Read-onlyIdempotent

Retrieves available Proxmox VE hosts with online status and per-host permission mode, so you can select a host before sending management requests.

Instructions

The Proxmox hosts Proxmox Controller lets you use, whether each is online, and what you may do on each (each kind of request is off, ask — the user approves it — or on). Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that — each host's online state and the off/ask/on permission mode governing each request type — but it never clarifies the permission model's practical effect or the result shape.

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?

It is a single short sentence, but it is a run-on with a broken opening phrase and the most valuable directive ("Call this first") buried at the end. Restructuring would make the same length far more useful.

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?

For a zero-parameter, no-output-schema, read-only enumeration tool, the agent needs only two things: what comes back (hosts, online status, permission mode) and when to call it (first). Both are present, so despite the clumsy wording nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema's empty object. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gestures at a list of Proxmox hosts with online status and per-host permission mode, but the opening clause ("The Proxmox hosts Proxmox Controller lets you use, whether each is online") is garbled and never states a clean verb+resource. An agent can infer it enumerates hosts, but only after parsing broken syntax.

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?

"Call this first" is an explicit, actionable ordering directive that tells the agent when to reach for this tool relative to all the sibling list/mutation tools. It stops short of naming alternatives or stating when-not-to-use, which keeps it out of 5 territory.

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