Skip to main content
Glama

Get node certificates

proxmox_get_node_certificates
Read-only

Lists a Proxmox node’s web/API TLS certificates, including CA, SSL, custom, and ACME certs, with subject, issuer, SANs, validity, days remaining, and fingerprint—without returning private keys.

Instructions

List the TLS certificates of a node's web interface/API (pve-root-ca, pve-ssl and any custom or ACME pveproxy-ssl certificate) with subject, issuer, SANs, validity, days left and fingerprint. Private keys are never returned.

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_certificates"
  }
}

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
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely useful behavior beyond that: it enumerates exactly which certificate objects are inspected and what attributes are returned, and it explicitly states private keys are never returned — a meaningful security-relevant assurance.

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?

One dense sentence, front-loaded with the action and resource, followed by returned fields and the private-key caveat. No filler, no redundancy with 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?

With no output schema, the description correctly compensates by listing the returned attributes (subject, issuer, SANs, validity, days left, fingerprint). Combined with the schema's node fallback documentation, an agent has what it needs; only the response shape/format (single object vs list per certificate) remains implicit.

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?

There is a single optional 'node' parameter and schema description coverage is 100%, including the PROXMOX_DEFAULT_NODE fallback and a pointer to proxmox_list_nodes. The description adds no meaning about the parameter beyond what the schema already provides, 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: 'List the TLS certificates of a node's web interface/API', then names the exact certificate objects (pve-root-ca, pve-ssl, custom/ACME pveproxy-ssl). An agent can distinguish this from generic node-info siblings like proxmox_get_node_config or proxmox_get_node_status immediately.

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?

The scope implies when to use it (inspecting web UI/API certs on a node), but there is no explicit when-to-use or when-not-to-use guidance and no routing to a sibling. Notably, proxmox_get_acme_account exists and the description mentions ACME certificates without clarifying the boundary between the two.

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