Skip to main content
Glama

pbs_traffic_control_upsert

Create or update a Proxmox Backup Server traffic control rule. Set rate limits for inbound and outbound bandwidth. Dry-run by default; set confirm=true to apply.

Instructions

MUTATION: create or update a PBS traffic-control (bandwidth-limit) rule. Dry-run by default.

Detects create-vs-update by reading the existing rule config (CAPTURE on update path): create → LOW: additive, no existing rule changed. update → MEDIUM: changing rate limits can throttle backups or saturate the network.

A too-low rate-in or rate-out throttles PBS backups to a crawl. No rollback primitive. confirm=True to execute.

POST (create) or PUT (update) /config/traffic-control[/{name}] Smoke-confirm: create-vs-update dispatch; rate-in/rate-out/burst-in/burst-out/timeframe param names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
commentNo
confirmNo
networkNo
rate_inNo
burst_inNo
rate_outNo
burst_outNo
timeframeNo
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 exist, so description carries full burden. It discloses mutation nature, dry-run default, risk levels, no rollback, and the HTTP methods (POST/PUT). It also mentions the dispatch logic and smoke-confirm tip.

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?

The description is well-structured with clear sections (MUTATION, risk levels, warnings, HTTP endpoints). It is slightly verbose but packs essential information. Good front-loading of purpose and safety.

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 10 parameters and no annotations, the description covers purpose, behavior, risks, and key parameters. It mentions the HTTP endpoints and create-vs-update dispatch. However, it lacks explanation for some parameters like network and comment, and the output schema existence could provide additional context.

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 only 10% (only proximo_target has description). The description adds context for rate-in, rate-out, burst-in, burst-out, timeframe by naming them as key params, but does not explain units or meaning of other fields like comment, network. Partial compensation.

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 is a mutation to 'create or update a PBS traffic-control (bandwidth-limit) rule.' It specifies the resource and distinguishes from sibling tools like pbs_traffic_control_delete or pbs_traffic_controls_list.

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 default and when to use confirm=True to execute. It differentiates risk between create (low) and update (medium) and warns about consequences of low rates. However, it does not explicitly mention alternatives or when not to use this tool.

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