Skip to main content
Glama

pmg_ruledb_rule_update

Update a PMG rule's name, priority, activity, direction, or group logic invert flags. Dry-run shows the plan; confirm executes the change.

Instructions

MUTATION (MEDIUM): update a PMG RuleDB rule configuration. Dry-run by default.

Changes rule-level fields only (name/priority/active/direction/AND-invert flags) — to attach or detach condition/action groups use pmg_ruledb_rule_from_attach and its sibling attach/detach tools. Only non-None fields are sent. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_YesRule ID (positive integer string, e.g. '100').
nameNoNew rule name; omit to keep current value.
activeNoWhether the rule is active; True begins live mail processing under this rule.
to_andNoAND (True) vs OR (False) logic across attached 'to' groups.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
from_andNoAND (True) vs OR (False) logic across attached 'from' groups.
priorityNoNew rule priority 0-100; lower numbers are evaluated with higher priority.
what_andNoAND (True) vs OR (False) logic across attached 'what' groups.
when_andNoAND (True) vs OR (False) logic across attached 'when' groups.
directionNoMail direction the rule applies to: 0=inbound, 1=outbound, 2=both.
to_invertNoIf True, invert the 'to' group match.
from_invertNoIf True, invert the 'from' group match.
what_invertNoIf True, invert the 'what' group match.
when_invertNoIf True, invert the 'when' group match.
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?

Despite no annotations, description fully discloses mutation nature, dry-run behavior, that only non-None fields are sent, and execution flow with confirm flag. It also specifies scope (rule-level fields only) and output format on execution.

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?

Three well-structured sentences: mutation label and purpose, sibling differentiation, and parameter/confirm behavior. No wasted words; front-loaded with essential information.

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?

For a mutation tool with 15 parameters and no annotations, the description covers scope, dry-run, execution, non-None behavior, and refers to sibling tools for group modifications. Output schema exists, so return values are covered.

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 coverage is 100% with detailed parameter descriptions. Description adds value by summarizing the parameter groups and noting that only non-None fields are sent, which is not in 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?

Description clearly states it updates PMG RuleDB rule configuration, lists specific rule-level fields (name/priority/active/direction/AND-invert flags), and distinguishes from sibling attach/detach tools.

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

Usage Guidelines5/5

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

Explicitly mentions dry-run by default, using confirm=True to execute, and directs to sibling tools for attaching/detaching condition/action groups, providing clear when-to-use and when-not-to-use guidance.

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