Skip to main content
Glama

pmg_action_removeattachments_create

Create a remove-attachments action object to strip attachments from emails and replace with custom text. Supports optional quarantine of removed attachments. Runs in dry-run mode by default; set confirm=true to execute.

Instructions

MUTATION (LOW): create a remove-attachments 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
all_NoIf True, remove all attachments; maps to API param 'all'.
infoNoOptional free-text description.
nameYesName for the new remove-attachments action object.
textYesReplacement text inserted in place of removed attachments.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
quarantineNoIf True, quarantine removed attachments instead of discarding them.
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 with low severity, dry-run default, and confirm flag behavior. Also mentions return format for executed call. No annotations provided, so description carries burden; covers safety profile well.

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?

Four sentences covering purpose, workflow, config, and behavior. Every sentence is useful and front-loaded.

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?

Complete for a creation tool: purpose, usage workflow, key parameters, behavior, and return format. With 7 parameters and output schema, description covers all essential aspects.

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?

Adds context beyond schema: explains 'text' as replacement text, 'all_' removes all attachments, 'quarantine' option, and confirm dry-run vs execute. Despite 100% schema coverage, description provides valuable added meaning.

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?

Clearly states it creates a remove-attachments action object in the PMG RuleDB, and differentiates from siblings like pmg_action_objects_list and pmg_ruledb_rule_action_attach.

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 references sibling tools for listing and attaching, explains dry-run default and confirm flag for execution, and mentions config requirement (PROXIMO_PMG_*).

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