Skip to main content
Glama

pmg_spam_config_update

Update Proxmox Mail Gateway spam filter settings with dry-run planning and selective field changes. Reset specific fields to defaults or set new values for Bayesian, Razor, RBL checks, and more.

Instructions

MUTATION (MEDIUM): update PMG spam filter configuration. Dry-run by default. confirm=True to execute. Needs PROXIMO_PMG_* config.

Only non-None fields are sent — omitted fields keep their current PMG value; delete resets named fields to defaults, effective immediately on new inbound mail. Read current values with pmg_spam_config. Dry-run returns a PLAN; confirm=True executes and returns {"status": "ok", "result": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deleteNoComma-separated field names to reset to their PMG defaults.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
use_awlNoWhether to enable the auto-whitelist; omit to leave unchanged.
languagesNoSpace-separated language codes used for spam language-based scoring; omit to leave unchanged.
use_bayesNoWhether to enable Bayesian spam classification; omit to leave unchanged.
use_razorNoWhether to enable Razor collaborative spam filtering; omit to leave unchanged.
rbl_checksNoWhether to enable RBL (realtime blocklist) checks; omit to leave unchanged.
maxspamsizeNoMaximum message size in bytes scanned for spam; omit to leave unchanged.
bounce_scoreNoSpam score threshold added for bounce/NDR-shaped messages; omit to leave unchanged.
extract_textNoWhether to extract text from attachments for spam scanning; omit to leave unchanged.
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.
wl_bounce_relaysNoWhitelisted bounce-relay hosts, space-separated; omit to leave unchanged.
clamav_heuristic_scoreNoSpam score added when ClamAV heuristic detection fires; omit to leave unchanged.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully covers behavior: it is a mutation, dry-run is default, confirm flag toggles execution, only non-None fields are sent, delete resets fields to defaults, effect is immediate on new inbound mail, and return values are described (PLAN vs status ok with result).

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 with 4 sentences, front-loading the tool's identity and purpose. Every sentence adds critical information without 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?

Given the complexity (13 parameters, mutation), the description covers dry-run, execution mode, parameter behavior, prerequisites, and return values. Output schema exists so return type detail is sufficient. Minor omission of error handling but acceptable for a well-documented 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 coverage is 100% so baseline is 3. The description adds value by explaining the overall parameter behavior ('Only non-None fields are sent... delete resets...') and suggests using pmg_spam_config for current values, which enhances context 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 clearly states 'update PMG spam filter configuration' with a specific verb and resource. It distinguishes itself from the sibling tool pmg_spam_config by explicitly recommending it for reading current values.

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 specifies a prerequisite ('Needs PROXIMO_PMG_* config') and explains when to use the confirm flag. It implicitly suggests using pmg_spam_config before updating, but does not explicitly list exclusions or alternatives beyond the read 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