Skip to main content
Glama

pbs_acme_account_create

Registers an ACME account with a Certificate Authority using a contact email. Offers a dry-run plan before executing.

Instructions

MUTATION: register a new ACME account with the CA. Dry-run by default.

Additive — does not affect any existing account. Pair with pbs_acme_plugin_create (DNS-01 challenge), then pbs_acme_cert_order, to actually issue a cert; to remove an account instead use pbs_acme_account_delete. confirm=True executes (POST /config/acme/account, synchronous — PBS returns null) and returns {"status": "ok", "result": None}; the default returns a dry-run PLAN dict. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName to register the account under; omit to let PBS assign a default name.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the account registration.
contactYesContact email address for the ACME account (CA renewal/expiry notices).
eab_kidNoKey identifier for External Account Binding; pairs with eab_hmac_key.
tos_urlNoURL of the CA's terms-of-service to accept; omit to accept the CA's default ToS.
directoryNoACME directory URL of the CA to register with; omit to use PBS's default CA.
eab_hmac_keyNoHMAC key for External Account Binding (required by some CAs, e.g. ZeroSSL). Redacted from the PLAN preview and the audit ledger, but IS sent to PBS on confirm=True.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It details mutation, dry-run default, additive nature, synchronous exec with null return on confirm=True, output format (PLAN dict vs. status dict), and config prerequisite 'Needs PROXIMO_PBS_* config'.

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?

Concise paragraph with no superfluous sentences. Front-loaded with key action and default behavior. Every sentence adds value: workflow guidance, behavior notes, config requirement.

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?

Given 8 parameters, no annotations, and an output schema present, the description covers essential workflow, return values, and prerequisites. It explains the dry-run mechanism, confirm behavior, and provides context for integration with other tools. Complete for the tool's complexity.

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?

Schema coverage is 100% with detailed descriptions. Description adds minimal extra parameter semantics beyond the schema (e.g., only the config dependency note). Baseline 3 is appropriate as description does not compensate for gaps but also does not add significant value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'register a new ACME account with the CA' with specificity. It distinguishes from sibling tools by naming pbs_acme_plugin_create, pbs_acme_cert_order, and pbs_acme_account_delete, indicating workflow and alternatives.

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

Usage Guidelines5/5

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

Explicit guidance: 'Pair with pbs_acme_plugin_create... then pbs_acme_cert_order' for issuing certs, and 'to remove an account instead use pbs_acme_account_delete'. Also explains dry-run vs. confirm=True, so the agent knows when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server