Skip to main content
Glama

pmg_who_object_add

Add an email, domain, IP, network, regex, or LDAP object to a PMG RuleDB 'who' object group. Dry-run by default; set confirm=True to apply immediately.

Instructions

MUTATION (LOW): add an object to a PMG RuleDB 'who' object group. Dry-run by default.

To create the group first use pmg_who_group_create; list its objects with pmg_who_group_objects. If the group is already attached to a rule, the new object affects mail matching immediately. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoIP address to match; required when type_='ip'.
cidrNoCIDR network to match; required when type_='network'.
modeNoLDAP lookup mode; used when type_='ldap'.
emailNoEmail address to match; required when type_='email'.
groupNoLDAP group name; used when type_='ldap'.
regexNoRegex pattern to match; required when type_='regex'.
type_YesObject type: email|domain|regex|ip|network|ldap — selects which sub-path/fields apply.
domainNoDomain to match; required when type_='domain'.
ogroupYesNumeric 'who' object group ID (e.g. '2') from pmg_who_groups_list.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
profileNoLDAP profile name; used when type_='ldap'.
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?

With no annotations, the description carries full disclosure burden. It declares the tool as a mutation (LOW), explains the dry-run default behavior via confirm=False, and details the effect of confirm=True. It also mentions that if the group is attached to a rule, changes affect mail matching immediately. Missing error handling details but covers key safety and side effects.

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 four sentences, each serving a distinct purpose: purpose declaration, prerequisite, real-world impact, and confirm behavior. It is concise with no extraneous words, and front-loads the key action.

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 tool's complexity (12 params, 2 required, output schema present), the description adequately covers purpose, prerequisites, side-effects, and confirm behavior. It does not explicitly distinguish from pmg_what_object_add or pmg_when_object_add, but the 'who' prefix in the name and sibling context is sufficient. The output schema is provided separately, so return values are not needed.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the confirm parameter's effect (plan vs. execution) and implicitly ties type_ to fields, but most parameter details are already in the schema. No significant new semantic information beyond what is already structured.

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 adds an object to a PMG RuleDB 'who' object group. The verb 'add' and resource 'object to a who object group' are specific, and the tool is distinguished from sibling 'pmg_who_' tools by focus on adding a single object.

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 provides prerequisites: use pmg_who_group_create to create the group first, and pmg_who_group_objects to list existing objects. It also notes the immediate effect if the group is attached to a rule. However, it does not explicitly mention alternatives like pmg_who_object_update for modifying existing objects, leaving some ambiguity.

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