Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

host_status

Read-onlyIdempotent

Retrieves CPU, memory, disk, uptime, load, and storage metrics for a Proxmox host by host ID so you can check node health and resource use.

Instructions

A host's nodes: CPU, memory, system disk, uptime, load, and storage use.

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>"
    },
    "name": "host_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 structurally. The description contributes the set of reported metrics, which is genuine added context, but says nothing about freshness, failure on an unknown host, or aggregation across nodes.

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 compact sentence with no filler, and the metric list is front-loaded. It loses a point only because the sentence lacks a leading verb phrase that would make the action unambiguous.

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

Completeness3/5

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

No output schema exists, so the field enumeration carries real weight in telling the agent what comes back, and it does so reasonably. Still missing is any verb framing or note on data freshness and per-node granularity, which matters for an inventory of hosts possibly having multiple nodes.

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?

With one parameter at 100% schema coverage, the schema already explains that host is the host id sourced from list_hosts. The description adds no further meaning about the parameter, so the baseline 3 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 enumerates what a host's status contains (CPU, memory, disk, uptime, load, storage) but is a noun fragment with no verb, so the agent must infer that this is a read of host status. It is distinguishable from mutation siblings like host_power or host_command, but it reads as a field list rather than a stated action.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative or exclusion. An agent could reasonably guess this is for checking host health versus guest_usage for VM-level metrics, but the definition never states that boundary.

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