Skip to main content
Glama

Get node subscription

proxmox_get_node_subscription
Read-only

Retrieve a Proxmox node's subscription status, level, product, socket count and next due date while keeping the subscription key hidden.

Instructions

Get a node's subscription status, level, product, sockets and next due date. The key itself is never shown.

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

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 covered. The description adds genuinely non-obvious context beyond that: 'The key itself is never shown,' warning the agent that the subscription secret is withheld so it doesn't attempt to retrieve it. It stops short of saying what is returned when no subscription exists.

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, zero filler, with the returned fields front-loaded and the secret-handling caveat last. Nothing could be removed without losing information.

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?

A simple, safe read tool with annotations covering safety, a fully described parameter, and no output schema — which the description partially compensates for by naming the returned fields. Slightly incomplete in not stating behavior for nodes without an active subscription.

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 `node` parameter's default resolution (PROXMOX_DEFAULT_NODE, single-node install, cross-reference to proxmox_list_nodes) is fully documented in the schema. The description adds nothing about parameters, so baseline 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 subscription status, level, product, sockets and next due date') and enumerates exactly what is retrieved. The resource is unambiguous against the sibling set, all of which target different node aspects (config, dns, stats, syslog).

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 resource name — this is the tool for subscription/compliance info — but there is no explicit when-to-use, no exclusion, and no pointer to an alternative. For a narrowly-scoped single-resource read tool this is adequate, though it leaves the agent to infer intent.

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