Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

proxmox_status

Read-only

Retrieve Proxmox VE version, cluster status, and resource usage to monitor node and cluster health.

Instructions

Get Proxmox VE version, cluster status, and resources

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": "proxmox_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointNoProxmox endpoint name from config (optional when exactly one is configured)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.22.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns version, cluster status, and resources, but does not add deeper behavioral context such as authentication requirements, limits, or return format.

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?

A single compact sentence that front-loads the key information with no wasted words.

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 simple read-only status tool with full schema coverage and no output schema, the description is largely complete: it names the main data categories returned. It could be slightly stronger by clarifying the relationship to sibling Proxmox inspection tools.

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%, so the single optional endpoint parameter is already fully documented. The description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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?

States a specific verb and resource: get Proxmox VE version, cluster status, and resources. It is clear what the tool does, but it does not explicitly distinguish itself from proxmox_guests, proxmox_node, or proxmox_tasks, which cover related Proxmox data.

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 description implies usage for an overall Proxmox VE status overview, but gives no explicit when-to-use guidance, exclusions, or alternatives such as proxmox_guests or proxmox_node. The intended context is inferable but not stated.

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

Deploy Server

Other Tools