Skip to main content
Glama

pmg_action_field_update

Update an existing field-modification action in Proxmox Mail Gateway RuleDB. Dry-run returns a plan; confirm=true executes the change.

Instructions

MUTATION (MEDIUM): update a field-modification action object in the PMG RuleDB. Dry-run by default.

id_ comes from pmg_action_objects_list; to create a new one instead use pmg_action_field_create. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_YesCompound action object ID (e.g. '13_26') from pmg_action_objects_list.
infoNoNew free-text description; omit to keep current value.
nameYesNew action object name; required (PMG rejects partial updates).
fieldYesNew mail header field to set; required (PMG rejects partial updates).
valueYesNew value to assign to the header field; required (PMG rejects partial updates).
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
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 behavior, dry-run default, execution trigger, and response format for both modes. No contradiction with annotations.

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?

Extremely concise: three sentences front-loading purpose, source, alternatives, and execution details. Every sentence provides essential information without redundancy.

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?

Given 7 parameters, no annotations, and presence of output schema, description completely covers purpose, differentiation, parameter sources, and behavior. Leaves no gaps for agent decision-making.

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

Parameters5/5

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

Beyond 100% schema coverage, description adds context: explains id_ source, reason why name/field/value are required (PMG rejects partial updates), and confirm parameter behavior. Adds meaningful semantics.

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 the tool updates a field-modification action object in PMG RuleDB. It uses specific verb 'update' and resource 'field-modification action object', distinguishing it from the create sibling tool.

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 explains dry-run default and execution with confirm=True. Directs user to obtain id_ from pmg_action_objects_list and to use pmg_action_field_create for creation, 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