Skip to main content
Glama

List ACME accounts

proxmox_list_acme_accounts
Read-only

List a Proxmox VE cluster's registered ACME accounts, including CA directory and contacts, to identify accounts used for ordering node certificates.

Instructions

List the cluster's registered ACME accounts (used to order node certificates), with their CA directory and contacts.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is carried. The description adds useful context about what comes back (CA directory and contacts) but says nothing about permissions, result size, or whether all accounts are always returned.

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 with no filler; the purpose comes first and the parenthetical clarification follows. 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.

Completeness3/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 does sketch the returned content, which is a genuine contribution. However, for a tool exposing two undocumented query parameters and no stated result shape beyond two fields, it leaves gaps an agent must guess at.

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?

Both parameters ('fields' and 'search') have 0% schema description coverage, and the description never mentions them. It names output fields (CA directory, contacts) rather than input semantics, so the agent gets no help on what 'fields' filters or how 'search' matches.

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?

Specific verb plus resource: 'List the cluster's registered ACME accounts', with a clarifying parenthetical that they are used to order node certificates. This distinguishes it from proxmox_list_acme_directories and proxmox_list_acme_plugins by resource, but the description never names the singular proxmox_get_acme_account sibling it most resembles.

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?

Provides no when-to-use or when-not-to-use guidance, and does not point to proxmox_get_acme_account for a single account or to the directories list. The agent must infer from the tool name alone that this is the bulk listing variant.

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