Skip to main content
Glama

pmg_action_field_create

Create a field-modification action object to set a mail header field value in Proxmox Mail Gateway rules. Use dry-run for planning before execution.

Instructions

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

List existing action objects with pmg_action_objects_list; attach this one to a rule with pmg_ruledb_rule_action_attach. Needs PROXIMO_PMG_* config. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoNoOptional free-text description.
nameYesName for the new field-modification action object.
fieldYesMail header field to set.
valueYesValue to assign to the header field.
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
Behavior4/5

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

Discloses mutation behavior, dry-run default, confirm parameter effect, and response format. No annotations provided, so description carries full burden. Config requirement mentioned. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact and efficient: first sentence states core purpose, then usage hints, then confirm behavior. No wasted words. Could benefit from clearer section separation.

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?

Covers essential aspects: purpose, dry-run, confirmation, config, related tools, and response. With output schema present, return values are sufficiently documented. Missing details about error handling or prerequisites beyond config.

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 3. Description adds context for 'confirm' (dry-run vs execute) and response structure, improving over schema alone for this key behavior.

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 field-modification action object in PMG RuleDB, with specific verb 'create' and resource 'field-modification action object'. It distinguishes from siblings like pmg_action_bcc_create and pmg_action_field_update by specifying the action type.

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?

Provides explicit guidance: dry-run by default, needs PROXIMO_PMG_* config, references related tools for listing and attaching. Does not explicitly state when not to use, but context of action types implies alternatives.

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