Skip to main content
Glama

pmg_node_syslog

Retrieve syslog entries from a Proxmox Mail Gateway node. Filter by service, time range, or limit results for analysis.

Instructions

READ-ONLY: get PMG node syslog entries. Needs PROXIMO_PMG_* config.

Returns a list of log-entry dicts. For a PVE hypervisor node's syslog use pve_node_syslog instead; for RRD performance data use pmg_node_rrddata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPMG node name; defaults to the configured node.
limitNoMaximum syslog entries to return.
sinceNoOnly return entries at or after this time (journalctl-style time spec).
startNoPagination offset into the syslog entries.
untilNoOnly return entries at or before this time (journalctl-style time spec).
serviceNoFilter syslog entries by service name.
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?

Description declares 'READ-ONLY' and mentions config requirement (PROXIMO_PMG_*). Specifies return format as list of log-entry dicts. Lacks details on pagination behavior or error cases, but covers key aspects.

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?

Two sentences plus return type statement. Front-loaded with 'READ-ONLY' and action. No unnecessary text.

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?

Coverage of 100% parameter descriptions in schema reduces burden on description. Describes return type and config dependency. Could explain pagination more, but sufficient given schema richness.

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

Parameters3/5

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

All 7 parameters have schema descriptions (100% coverage). Description adds no extra parameter-level meaning beyond what's in 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?

Description clearly states 'get PMG node syslog entries' with verb and resource. Distinguishes from siblings pve_node_syslog and pmg_node_rrddata explicitly.

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 alternatives for PVE nodes and RRD data. Also designates tool as 'READ-ONLY' signaling safe usage.

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