Skip to main content
Glama

pmg_ruledb_rule_update

Modify a Proxmox Mail Gateway RuleDB rule. Update optional fields such as name, priority, and conditions; requires explicit confirmation to apply changes.

Instructions

MUTATION (MEDIUM): update a PMG RuleDB rule configuration. Dry-run by default. confirm=True to execute. Needs PROXIMO_PMG_* config. PMG 9.1 pmgsh-verified path: PUT /config/ruledb/rules/{id}/config. id_: rule ID (positive integer string, e.g. '100'). All other fields are optional; only non-None values are sent. WARNING: setting active=True activates the rule and begins live mail processing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_Yes
nameNo
activeNo
to_andNo
confirmNo
from_andNo
priorityNo
what_andNo
when_andNo
directionNo
to_invertNo
from_invertNo
what_invertNo
when_invertNo
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 exist, so the description fully carries the burden. It discloses mutation severity (MEDIUM), dry-run behavior, need for confirm, config requirement, and a warning about active=True activating live mail processing. It does not discuss rollback or idempotency, but covers key behavioral traits.

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 (5 sentences) and front-loaded with key info (MUTATION, dry-run). Every sentence adds value with no redundancy.

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?

An output schema exists, so return values need not be explained. The description covers mutation, dry-run, confirm, required param, optional fields, and a critical warning. It does not elaborate on prerequisites beyond config or the response structure, but is thorough for a mutation tool.

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

Parameters4/5

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

Schema description coverage is only 7% (only proximo_target has a schema description). The description compensates by explicitly explaining id_ and stating 'All other fields are optional; only non-None values are sent', which conveys semantics for all parameters without listing each. The warning adds meaning for active.

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?

The description clearly states the tool updates a PMG RuleDB rule configuration and includes specific details like dry-run and confirm flag. It distinguishes from create/delete/get by the verb and context, but does not explicitly differentiate from sibling rules tools (e.g., pmg_ruledb_rule_create).

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

Usage Guidelines3/5

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

The description explains dry-run default and confirm=True to execute, providing clear usage context. However, it does not explicitly state when NOT to use this tool or mention alternatives like create or delete.

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