Skip to main content
Glama

Get group

proxmox_get_group
Read-only

Fetch a Proxmox group's members and associated comment by group ID to inspect group composition and details.

Instructions

Get a group's members and comment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "groupid": "<groupid>"
    },
    "name": "proxmox_get_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupidYesGroup ID (see proxmox_list_groups)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.2/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 structurally. The description adds that the call returns the group's members and comment, which is useful output context, but says nothing about error behavior for a missing group or any permission requirements.

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 short sentence with the resource and the return contents front-loaded; nothing is redundant. It is terse to the point of omitting any usage framing, but there is no filler to cut.

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-only lookup with full schema coverage, no output schema, and complete annotations, the description covers purpose and return contents adequately. Only the absence of any guidance on group ID discovery or failure cases keeps it from a 5.

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?

With a single parameter and 100% schema description coverage, the schema already explains that groupid is the group identifier and points to proxmox_list_groups for discovery. The description adds no further meaning about format or constraints, which matches the baseline 3 expectation when the schema does the work.

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 states a concrete verb and resource ('Get a group') and even specifies the returned content ('members and comment'), so the agent knows what comes back. It does not explicitly distinguish itself from look-alike siblings such as proxmox_get_ha_group, but the resource named is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance in the description, and no named alternative. The only routing hint — see proxmox_list_groups for IDs — lives in the schema, not the description.

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