Skip to main content
Glama

pmg_ruledb_rule_create

Create a RuleDB rule for Proxmox Mail Gateway. Starts as a shell with dry-run mode to plan changes; activate with confirm=True.

Instructions

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

Creates the rule shell only — attach condition/action groups afterward with pmg_ruledb_rule_from_attach and its sibling attach tools; list existing rules with pmg_ruledb_rules_list. active defaults False (live mail is affected only once active). confirm=True executes and returns {"status": "ok", "result": }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new RuleDB rule.
activeNoWhether the rule is active on creation; defaults False since active rules affect live mail processing.
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.
priorityYesRule 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
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses mutation, dry-run by default, confirm flag, active default false, and that it only creates a shell. Does not mention rate limits or auth, but overall behavioral traits are well-covered.

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?

Two paragraphs with a bold summary line. No fluff, every sentence adds value. Front-loaded with key info (mutation, dry-run). Efficient structure.

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 14 parameters and complexity, description explains the overall workflow (create shell then attach) and references sibling tools. Output schema exists so return is covered. Schema covers individual parameters. Description is complete enough for effective use.

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%, baseline 3. Description adds value by explaining confirm's dry-run vs execute behavior and active default meaning. For other parameters, schema descriptions are detailed. Description adds context beyond schema for key parameters.

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 PMG RuleDB rule, distinguishes by noting it creates only the 'shell' and referencing sibling attach tools. It also mentions dry-run default. This provides a specific verb+resource with clear differentiation from related tools.

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?

The description explains when to use: to create a rule shell, then attach condition/action groups with pmg_ruledb_rule_from_attach etc. It also advises listing rules with pmg_ruledb_rules_list. It does not explicitly state when not to use, but context makes it clear. Good guidance on the confirm flag and active default.

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