Skip to main content
Glama

Get ACME account

proxmox_get_acme_account
Read-only

Retrieve ACME account details—CA directory, account URL, status, contacts, and accepted terms—with keys redacted, so you can verify certificate account settings.

Instructions

Get an ACME account's details: CA directory, account URL (location), status, contacts and accepted terms of service. Keys are redacted.

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

Input Schema

NameRequiredDescriptionDefault
nameNoAccount name (default 'default')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/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 one genuinely useful behavioral fact — that keys are redacted in the response — but says nothing about permissions, errors when the account does not exist, or the response shape.

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 front-loaded sentence that identifies the resource and then lists the returned fields; no filler. The field enumeration is useful rather than wasteful.

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 read-only, single-parameter tool with no output schema, the description does the needed work by enumerating returned fields and flagging key redaction. Only the absence of any guidance relative to the accounts-listing sibling keeps it from being fully complete.

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?

Only one parameter exists and schema description coverage is 100%, with the default 'default' documented in the schema itself. The description adds no meaning beyond that, so the baseline 3 applies.

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?

Names a specific verb and resource ("Get an ACME account's details") and enumerates what is returned: CA directory, account URL/location, status, contacts and accepted terms. It is clearly a single-account read, distinguishable from list-style siblings by the singular resource, though it never names the sibling it complements.

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 only implied by the defaultable single 'name' argument — an agent can infer this fetches one account's details rather than enumerating accounts, but there is no explicit when-to-use/when-not guidance and no mention of the listing tool as an alternative.

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