Skip to main content
Glama

pmg_domain_create

Create a managed mail domain. Dry-run returns a plan; set confirm=True to execute the actual creation.

Instructions

MUTATION (LOW): create a managed mail domain. Dry-run by default. confirm=True to execute. Needs PROXIMO_PMG_* config.

domain: domain name to add (e.g. 'example.com'). Dry-run returns a PLAN; confirm=True executes and returns {"status": "ok", "result": ...}. Additive — reverse with pmg_domain_delete; list current domains with pmg_domains_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to add as a managed mail domain, e.g. 'example.com'.
commentNoOptional free-text comment stored with the domain.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
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
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses mutation type, dry-run vs execution behavior, and return types (PLAN vs status/result). It also notes the tool is additive and reversible, adding behavioral context.

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?

The description is concise, with no redundant sentences. It front-loads the key action and default behavior, then provides necessary details in a logical order. Every sentence is informative.

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?

Given the presence of an output schema and the complexity of 4 parameters, the description covers the tool's behavior, configuration needs, and relationship to siblings. It could mention potential errors or permissions, but overall it is adequate.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all parameters. The description adds extra context for the 'domain' parameter (example format) and clarifies the return behavior for 'confirm'. This provides meaningful information beyond the schema.

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?

The description clearly states the tool creates a managed mail domain, specifies it is a mutation, and distinguishes it from siblings by mentioning pmg_domain_delete and pmg_domains_list. This directly differentiates the tool's purpose.

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

Usage Guidelines4/5

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

The description explains dry-run by default and confirm=True to execute, and mentions required configuration (PROXIMO_PMG_*). It does not explicitly state when not to use the tool, but the sibling mentions imply alternatives. Clear context for usage.

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