Skip to main content
Glama

Get cluster log

proxmox_get_cluster_log
Read-only

Retrieve recent Proxmox cluster log entries from all nodes, including task starts and stops, logins and other cluster events, with filtering and entry limits.

Instructions

Read recent entries of the cluster log (task starts/ends, logins and other cluster events from all nodes).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_get_cluster_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoMaximum number of entries (default 50)
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety and side-effect behavior are covered. The description adds that entries span all nodes and what event classes appear, but says nothing about ordering, recency window, or truncation behavior beyond 'recent'.

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?

A single front-loaded sentence with the core purpose first and the parenthetical event examples second. The parenthetical earns its place by clarifying what the log contains; nothing is redundant.

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?

For a simple read-only log tool with annotations covering safety, fully described parameters, and no output schema, the description supplies the essential missing context: cross-node scope and the event types returned. Only the ordering/recency semantics remain underspecified, which is a minor gap.

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?

Schema description coverage is 100%, so both the max cap/default and the case-insensitive substring search are fully documented in the schema. The description contributes no additional meaning about how filtering or limits interact with the 'recent entries' window, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Read) and resource (cluster log), then scopes it to 'all nodes' and enumerates the kinds of events returned (task starts/ends, logins). That content list implicitly separates it from siblings like proxmox_get_task_log or proxmox_get_firewall_log, but no sibling is named explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description of what the log contains, which lets an agent infer this is the tool for broad cluster-wide event history rather than per-task or per-subsystem logs. There is no explicit when-to-use statement and no mention of when to prefer proxmox_get_task_log, proxmox_get_ceph_log, or the other log siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools