Skip to main content
Glama

pbs_metrics_influxdb_udp_create

Create a Proxmox Backup Server InfluxDB UDP metrics server configuration. Use confirm=true to execute, otherwise returns a plan.

Instructions

MUTATION: create a PBS InfluxDB udp metrics server configuration.

RISK_LOW: matches PVE's pve_metrics_server_set baseline exactly — no credential field exists on this sub-plane at all (schema-verified). Dry-run by default (returns a PLAN); confirm=True executes (POST /config/metrics/influxdb-udp, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mtuNoThe MTU. Defaults to 1500 server-side if omitted; no upper bound stated by the schema.
hostYeshost:port combination (host can be a DNS name or IP address; port REQUIRED), e.g. '192.0.2.10:8089'.
nameYesNew Metrics Server ID (3-32 chars, alnum/underscore start, then alnum/./_/-).
enableNoEnables or disables the metrics server. Defaults True server-side if omitted.
commentNoComment (<=128 chars, no control chars).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
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
Behavior5/5

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

No annotations provided, so description carries full burden. It details mutation behavior, risk level (RISK_LOW), dry-run vs execution, synchronous endpoint, and response structure. Provides a thorough behavioral account beyond what schema offers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is dense and front-loaded with key information, but could be more organized. Every sentence adds value; no fluff. Structured with labels (MUTATION:, RISK_LOW:).

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

Completeness5/5

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

Given 7 parameters, no annotations, and no output schema shown, description covers purpose, usage, risk, dry-run behavior, return format, and prerequisites comprehensively. Leaves no critical gaps for an agent to invoke correctly.

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 coverage is 100%, so baseline is 3. Description adds minimal extra meaning beyond schema; e.g., dry-run behavior is already implied by confirm parameter. No significant enrichment of parameter semantics.

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 it creates a PBS InfluxDB UDP metrics server configuration, specifying the action (MUTATION), resource, and providing detailed context. It distinguishes itself from siblings like HTTP-based tools through the UDP-specific naming and context.

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?

It explains dry-run by default with confirm=True to execute, and mentions prerequisite config ('Needs PROXIMO_PBS_* config'). However, it does not explicitly compare with alternatives like pbs_metrics_influxdb_http_create, which would help in tool selection.

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