Skip to main content
Glama
Sign In
Proxmox MCP Server

Proxmox MCP Server

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_cluster_resources

Read-only

Retrieve all resources in a Proxmox cluster, with optional filtering by type such as VM, storage, node, or SDN.

Instructions

Get all cluster 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": "get_cluster_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoResource type filter: vm, storage, node, sdn

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/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 clear. However, the description adds no behavioral context beyond the name. It says 'all' but the parameter allows filtering, which is slightly misleading. No mention of pagination, output format, or auth requirements.

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?

The description is a single short sentence with no wasted words, but it sacrifices informativeness for brevity. It is front-loaded but lacks sufficient detail to be fully effective.

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

Completeness2/5

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

The description does not explain the return format, how to interpret results, or how to use the filter parameter. With no output schema, the description should provide more context to be complete. The tool is a listing operation and sibling tools suggest detailed listing capabilities, yet this description is minimal.

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?

The input schema covers 100% of the one parameter with a description. The tool description does not add any additional meaning or usage hints for the parameter, so the baseline score of 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 'Get all cluster resources' states the verb and resource clearly, but it is vague about what constitutes 'cluster resources' and does not differentiate it from sibling list tools like list_vms or list_storage. The presence of a filter parameter suggests it returns a subset, contradicting 'all'.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where other tools (e.g., list_vms for VMs only) might be more appropriate.

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