Skip to main content
Glama

Get Proxmox VE version

proxmox_get_version
Read-only

Fetches the Proxmox VE version and release from the connected API endpoint to verify environment and compatibility details.

Instructions

Get the Proxmox VE version and release of the API endpoint this server talks to.

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_get_version"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description's added value is that the returned version describes the proxied API endpoint rather than the local server. It does not disclose what fields (version, release, repo id) come back, and the idempotentHint=false annotation for a read-only version call goes unremarked.

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 front-loaded sentence with no filler; the disambiguating clause about the API endpoint is placed where it does the most work.

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 parameterless read tool with annotations and no output schema, the description covers what is needed to select and call it. A brief note on what the response contains (version/release fields) would close the last gap.

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 no parameter meaning to convey; the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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?

The description names a specific verb and resource (Proxmox VE version and release) and clarifies that it is the version of the API endpoint the server talks to, not the MCP server itself. That scoping distinguishes it from the many sibling get_* resource tools, though it does not explicitly reference any of them.

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?

No explicit statement of when to call this versus alternatives or of any prerequisites, but for a zero-parameter version probe the intended use (checking API/version availability) is strongly implied. Adequate, with clear room for a one-line 'use before version-dependent operations' cue.

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