Skip to main content
Glama

pmg_who_group_delete

Delete a PMG 'who' object group and all its objects. Use pmg_who_groups_list to find the group ID. Confirm execution with confirm=True; dry-run by default.

Instructions

MUTATION (MEDIUM): delete a PMG RuleDB 'who' object group. Dry-run by default.

Irreversible — also removes every object within the group. List groups first with pmg_who_groups_list; to remove just one object instead use pmg_who_object_delete. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ogroupYesNumeric 'who' object group ID (e.g. '2') from pmg_who_groups_list.
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?

Discloses mutation, dry-run default, irreversibility, and that it removes objects within the group. Lacks authorization or rate limit info, but given no annotations, this is adequate.

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, front-loaded with key info (mutation, dry-run), provides sequential usage hints without unnecessary verbosity.

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?

Covers prerequisite, alternative, and execution workflow. Missing explicit description of dry-run output format, but output schema may cover that. Overall sufficient for safe use.

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%, and description adds minimal value beyond the existing parameter descriptions. The schema already describes ogroup, confirm, and proximo_target adequately.

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?

Clearly states 'delete a PMG RuleDB who object group', distinguishes from sibling pmg_who_object_delete which removes a single object. Also mentions listing groups first with pmg_who_groups_list.

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?

Explicitly says to list groups first and provides alternative tool for single object removal. Also explains dry-run default and confirm=True for actual execution.

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