Skip to main content
Glama

pmg_tasks_list

List tasks on a Proxmox Mail Gateway node, with filters for errors, time range, task type, user, and status.

Instructions

READ-ONLY: list PMG tasks on a node. Needs PROXIMO_PMG_* config.

Returns a list of task dicts. errors=True returns only failed tasks. For a PVE hypervisor node's tasks use pve_tasks_list instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPMG node name; defaults to the configured node.
limitNoMaximum tasks to return.
sinceNoUnix epoch: only tasks started at or after this time.
startNoPagination offset into the task list.
untilNoUnix epoch: only tasks started at or before this time.
errorsNoIf True, return only failed tasks.
typefilterNoFilter tasks by task type.
userfilterNoFilter tasks by the user that started them.
statusfilterNoFilter tasks by status text.
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?

The description explicitly marks the tool as READ-ONLY, discloses the return format (list of task dicts), and explains the errors parameter. While no annotations exist, this level of transparency is good but could mention pagination behavior.

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: 3 sentences covering purpose, config, return type, parameter clarification, and alternative. No wasted words.

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 high parameter count and many siblings, the description adequately covers key aspects: what it does, config requirement, return type, and key parameter (errors). The presence of output schema and full schema descriptions compensate for minor omissions.

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?

All parameters have schema descriptions, but the tool description adds context by explaining the 'errors' parameter clearly. No redundant info.

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 uses the verb 'list' with the resource 'PMG tasks on a node' and explicitly differentiates from pve_tasks_list, making the purpose clear and distinct.

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?

Provides explicit guidance on when to use (PMG node tasks) and when to use the sibling pve_tasks_list instead. Also states a config prerequisite.

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