Skip to main content
Glama

pmg_quarantine_attachment

Read and list quarantined email attachments from Proxmox Mail Gateway, filterable by user mailbox and time range for security review.

Instructions

READ-ONLY: list attachment quarantine entries. Needs PROXIMO_PMG_* config.

Returns a list of dicts, one per quarantined attachment. pmail defaults to the authenticated user when omitted. For spam quarantine use pmg_quarantine_spam; to act on entries use pmg_quarantine_action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoUnix epoch end of the window; omit for no upper bound.
pmailNoScope the attachment quarantine read to this user's mailbox; defaults to the authenticated PMG user.
startNoUnix epoch start of the window; omit for no lower bound.
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?

Declares READ-ONLY, describes return type as list of dicts, and notes default pmail behavior. Lacks details on rate limits or error conditions, but adequate for a read-only list tool.

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?

Three efficient sentences, front-loaded with 'READ-ONLY', no 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?

Covers purpose, usage, return format, and config needs. Output schema exists, so no need to detail return values.

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?

With 100% schema coverage, baseline is 3. The description adds value by noting pmail defaults to authenticated user, enhancing understanding 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?

Clear verb 'list' and resource 'attachment quarantine entries'. Distinguishes from siblings 'pmg_quarantine_spam' and 'pmg_quarantine_action'.

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 states it's read-only, mentions config requirement, and provides alternatives for spam quarantine and actions.

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