Skip to main content
Glama

Get node time and time zone

proxmox_get_node_time
Read-only

Retrieves a Proxmox node's current UTC time, local time, and configured time zone to help detect clock drift between cluster nodes.

Instructions

Get a node's current time (UTC), local time and configured time zone. Useful for spotting clock drift between 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_node_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/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 profile are covered. The description adds the useful behavioral detail that it returns both UTC and local time plus the configured zone (explaining why it is non-idempotent), but says nothing about permissions, failure modes, or how a missing/offline node is reported.

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 short sentences, front-loaded with what is returned and followed by the diagnostic use case. There is no filler, hedging, or repetition of the title.

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 one-parameter read tool with no output schema, the description names the returned values well enough for an agent to know what to expect. Minor gaps remain around error/edge behavior for unreachable nodes, but nothing essential for correct invocation is missing.

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 coverage is 100% and the single optional 'node' parameter is already documented in the schema, including the PROXMOX_DEFAULT_NODE fallback and the pointer to proxmox_list_nodes. The description adds no syntax, naming convention, or default-resolution detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get a node's current time (UTC), local time and configured time zone') and even enumerates the three values returned. No sibling in the listed catalog retrieves time/timezone, so the resource itself cleanly separates this from status, stats, and DNS tools.

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

Usage Guidelines4/5

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

Gives a concrete motivating scenario: 'Useful for spotting clock drift between nodes,' which tells the agent when this tool is the right call. It stops short of explicit exclusions or naming an alternative for adjacent questions (e.g. timezone configuration changes), so it is clear context rather than full routing guidance.

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