Skip to main content
Glama

pmg_when_group_update

Update a PMG 'when' object group configuration, such as renaming or changing logic and inversion. Dry-run by default; use confirm=True to apply changes.

Instructions

MUTATION (MEDIUM): update a PMG RuleDB 'when' object group config. Dry-run by default.

Renames or reconfigures the group itself; to change its timeframes use pmg_when_object_add/pmg_when_object_update/pmg_when_object_delete. Only non-None fields are sent, others keep their current value. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
and_NoAND (True) vs OR (False) logic across group members; maps to API param 'and'.
infoNoNew free-text description; omit to keep current value.
nameNoNew name for the group; omit to keep current value.
invertNoIf True, invert the group's match result.
ogroupYesNumeric 'when' object group ID (e.g. '4') from pmg_when_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?

With no annotations, the description discloses key behaviors: dry-run default, confirm execution, partial updates (only non-None fields sent), and response format for confirm. Could mention idempotency or error handling, but covers core mutation behavior well.

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?

Two sentences plus a confirm line, all front-loaded with essential info. No wasted words, every sentence adds value. Structured logically.

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 7 parameters, 1 required, and existing output schema, the description covers dry-run, confirm, partial update, and sibling tool differentiation. Lacks mention of prerequisites (group must exist) and potential side effects, but these are implied for update operations.

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 descriptive field descriptions. The description adds the behavioral detail that only non-None fields are sent, but otherwise param semantics are fully covered by the schema, meeting the baseline.

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 it updates a PMG RuleDB 'when' object group config, with specific verb 'update' and resource 'PMG RuleDB 'when' object group'. It distinguishes itself from sibling tools for timeframes (pmg_when_object_add/update/delete) and from create/delete/get/list tools.

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?

Explicitly states dry-run by default and confirm=True to execute. Directs users to other tools for timeframes changes. Does not explicitly list prerequisites or when to use this vs. alternative group update tools, but the differentiation is clear from context.

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