Skip to main content
Glama

pbs_metrics_influxdb_http_create

Create a metrics server endpoint for sending PBS metrics to InfluxDB via HTTP. Dry-run by default to preview changes; set confirm=True to execute.

Instructions

MUTATION: create a PBS InfluxDB http metrics server configuration.

RISK_MEDIUM: this sub-plane can hold a stored API token — mirrors pbs_s3_client_create's credential-bearing-create reasoning, a step up from PVE's LOW-rated pve_metrics_server_set (whose currently-shipped tool surface doesn't expose a token parameter at all, even though PVE's own schema has one — pbs_metrics.py module docstring's 2026-07-15 correction). SECRET CONTRACT: token is NEVER written to the audit ledger or the dry-run PLAN — forwarded RAW only to the real PBS API on confirm=True (the create must actually work). Dry-run by default (returns a PLAN); confirm=True executes (POST /config/metrics/influxdb-http, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHTTP(s) url with optional port, e.g. 'https://influx.example.com:8086'.
nameYesNew Metrics Server ID (3-32 chars, alnum/underscore start, then alnum/./_/-).
tokenNoAPI token. SECRET — never written to the audit ledger or the dry-run PLAN.
bucketNoInfluxDB Bucket (1-32 chars). Defaults to 'proxmox' server-side if omitted.
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.
verify_tlsNoIf true, the endpoint's certificate is validated. Defaults True server-side if omitted.
organizationNoInfluxDB Organization (1-32 chars). Defaults to 'proxmox' server-side if omitted.
max_body_sizeNoMaximum body size in bytes. Defaults to 25000000 server-side if omitted; no upper bound stated by the schema.
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?

Discloses key behaviors: mutation, dry-run default, confirm flag execution, token secrecy (not written to audit or plan), synchronous API call, and configuration needs. Lacks error handling details but sufficient for most agent decisions.

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

Conciseness2/5

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

Contains irrelevant internal notes (e.g., module docstring date correction) that do not aid tool selection. The description is verbose and could be streamlined.

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?

Covers behavioral aspects thoroughly but lacks usage guidelines and could be more structured. Given the tool's complexity (11 params, secret handling), it is adequate but not fully complete.

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?

Input schema has 100% coverage with descriptions for all 11 parameters. The description adds token secrecy context but does not significantly enhance parameter understanding beyond the schema.

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 starts with 'MUTATION: create a PBS InfluxDB http metrics server configuration', clearly stating the action (create) and resource. It distinguishes from sibling tools like delete, update, get, and list.

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?

No explicit guidance on when to use this tool versus alternatives. It mentions risk level and comparison to pve_metrics_server_set but does not provide clear when/when-not instructions.

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