Skip to main content
Glama

List realms

proxmox_list_realms
Read-only

List Proxmox VE authentication realms with their type, TFA provider, and comment to inspect configured PAM, PVE, LDAP, Active Directory, or OpenID Connect sources.

Instructions

List authentication realms (pam, pve, LDAP, Active Directory, OpenID Connect) with type, TFA provider and comment.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3/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 adds value by disclosing what each entry contains (type, TFA provider, comment), but it says nothing about permissions needed, ordering, or result size. The idempotentHint=false on a pure list operation is left unexplained.

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?

One front-loaded sentence with no filler; the parenthetical realm-type list is informative rather than padding. It could be marginally tighter, but nothing is wasted.

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

Completeness3/5

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

For a simple read-only list tool with no output schema, the description covers the resource and returned fields adequately. However, with 0% schema coverage on both parameters and no output schema, the definition leaves the agent without any explanation of how to filter or project results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%: the two parameters 'fields' and 'search' have no descriptions at all. The description never mentions either, so an agent must guess that 'fields' projects columns and 'search' filters realms — a significant gap the description should have closed.

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 gives a specific verb and resource ('List authentication realms') and even enumerates the realm types covered (pam, pve, LDAP, Active Directory, OpenID Connect), which unambiguously separates it from the many other proxmox_list_* siblings. It stops short of naming or contrasting any alternative tool, but the resource itself is distinctive enough that an agent can route to it.

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 guidance about when to call this versus other list tools, no prerequisites (e.g. required permissions), and no note about pagination or scoping. Usage is only implied by the tool name and resource type.

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