Skip to main content
Glama

List metric servers

proxmox_list_metric_servers
Read-only

Lists external metric servers (InfluxDB, Graphite, OpenTelemetry) configured in Proxmox VE so you can verify where performance data is sent.

Instructions

List external metric servers (InfluxDB, Graphite, OpenTelemetry) that Proxmox sends performance data 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_list_metric_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.1/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 and locality are covered. The description contributes useful domain framing (these are targets Proxmox pushes performance data to), but says nothing about whether it returns configured targets only or live/health status, nor about ordering or result volume.

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 parenthetical examples earn their place by clarifying scope. Nothing to trim and nothing buried.

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?

For a simple read-only list tool this covers the essential purpose, and no output schema means return values need not be described. However, with two fully undocumented parameters and no note on scoping or filtering, the definition is only minimally sufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, and the description never mentions them. 'fields' (array of strings) and 'search' (string) are left completely unexplained — an agent cannot tell whether fields is a projection selector or something server-specific, or whether search matches names, types, or hosts.

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 ('List') and resource ('external metric servers'), and names the concrete backends (InfluxDB, Graphite, OpenTelemetry) so the agent knows exactly what kind of object is returned. It is not differentiated in prose from any sibling, but the siblings listed are plainly different resources (ACL, backups, Ceph pools), so confusion risk is low.

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 when-to-use guidance, no prerequisites (e.g. cluster/node context, permissions), and no mention of an alternative tool or condition under which this should not be called. The agent must infer everything from the one-sentence purpose.

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