Skip to main content
Glama

Get cluster (corosync) configuration

proxmox_get_cluster_config
Read-only

Retrieve Corosync cluster configuration details, including member nodes, IDs, votes, link addresses, totem settings, and join information for adding nodes to a Proxmox VE cluster.

Instructions

Get the corosync cluster configuration: member nodes with their IDs, votes and link addresses, the totem settings, and the join information (fingerprint, addresses) used to add 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_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior3/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's contribution is naming the returned data (member nodes, votes, link addresses, totem settings, join fingerprint), which is payload detail rather than behavioral disclosure such as permission requirements or caveats about secrets in join info.

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?

A single front-loaded sentence that names the resource first and then enumerates the payload; every listed item (votes, link addresses, totem, fingerprint) is substantive and none of the wording is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description carries the burden of describing return values, and it does so concretely enough that an agent can decide whether this tool yields the information it needs. It is complete for a parameterless read tool whose annotations already cover safety.

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?

The tool takes zero parameters, so per the baseline this dimension is adequate without any parameter discussion in the description; there is nothing for the description to disambiguate.

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 uses a specific verb+resource ('Get the corosync cluster configuration') and enumerates the contents (member nodes with IDs/votes/link addresses, totem settings, join fingerprint/addresses). This makes it distinguishable from cluster status/options/log siblings by content rather than by naming them explicitly, so it stops just 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?

No explicit when-to-use or when-not-to-use guidance and no sibling is named. The only usage signal is implicit: the join information is described as 'used to add nodes', hinting at node-enrollment workflows, but the agent must infer that this is the static-config counterpart to proxmox_get_cluster_status.

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