Skip to main content
Glama

pve_metrics_server_set

Create or update a PVE metrics server definition. Dry-run returns a plan; set confirm=true to execute and apply new metrics forwarding settings immediately.

Instructions

MUTATION: create-or-update a PVE metrics server definition. Dry-run by default (returns a PLAN); confirm=True executes and returns {"status": "ok", "result": null} (no further payload). Config-only — metrics forwarding adjusts to the new settings immediately; no snapshot primitive, so re-apply this same tool to revert. To remove it use pve_metrics_server_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoTCP/UDP port the metrics server listens on
serverNoHostname or IP address of the metrics server
commentNoOptional free-text comment stored with the metrics server definition
confirmNoFalse (default) returns a dry-run PLAN only; True executes the create/update
disableNoTrue disables forwarding to this metrics server without deleting the definition
metrics_idYesUnique ID of the metrics server definition to create or update
metrics_typeNoMetrics backend type, e.g. 'influxdb' or 'graphite'
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the dry-run behavior, return values (PLAN vs status ok), immediate config application, and absence of snapshot primitive. It does not cover auth needs or rate limits but provides substantial transparency for a mutation tool.

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?

The description is concise, three sentences, each providing key information: mutation type, dry-run/execute behavior, and config-only nature with revert guidance. No unnecessary 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?

Given the tool's complexity (mutation, 8 parameters, no annotations, output schema exists), the description covers essential behaviors: return formats, dry-run, confirm, immediate effect, and revert method. It does not detail prerequisites or output schema, but both are covered by structured data. Minor gap: no mention of create-vs-update distinction.

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%, baseline is 3. The description adds context about the confirm parameter (dry-run vs execute) but does not elaborate on other parameters beyond what the schema already provides. The schema itself is descriptive, so the description adds marginal value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates or updates a PVE metrics server definition. It distinguishes itself from sibling tools by explicitly mentioning pve_metrics_server_delete for removal.

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

Usage Guidelines4/5

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

The description provides clear usage guidance: dry-run by default, confirm=True for execution, and notes that re-applying the same tool can revert changes. It also references the delete tool for removal, offering an alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server