Skip to main content
Glama

pmg_action_notification_update

Update an existing notification action object in PMG RuleDB. Use with id from pmg_action_objects_list; dry-run by default, set confirm=True to execute.

Instructions

MUTATION (MEDIUM): update a notification action object in the PMG RuleDB. Dry-run by default.

id_ comes from pmg_action_objects_list; to create a new one instead use pmg_action_notification_create. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesNew notification recipient email address; required (PMG rejects partial updates).
id_YesCompound action object ID (e.g. '13_26') from pmg_action_objects_list.
infoNoNew free-text description; omit to keep current value.
nameYesNew action object name; required (PMG rejects partial updates).
attachNoIf True, attach the original message to the notification.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
subjectYesNew notification subject line; required (PMG rejects partial updates).
body_textYesNew notification body text; maps to API param 'body'; required (PMG rejects partial updates).
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 nature, dry-run default, confirm execution behavior, and return format. No annotations exist, so description carries full burden; could mention error behavior or reversibility.

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?

Three concise sentences, front-loaded with mutation type, no fluff, each sentence adds value.

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 100% schema coverage and existence of output schema, description adequately explains id_ sourcing, dry-run, confirm, and create alternative. Could mention dry-run plan output, but not essential.

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 covers all parameters; description adds source of id_, explains required fields rationale (PMG rejects partial updates), and maps body_text to API param. Adds meaningful context beyond 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?

Clearly states it updates a notification action object in the PMG RuleDB, distinguishing from create via explicit sibling mention.

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?

Specifies prerequisite (id_ from pmg_action_objects_list), alternative (use create for new), and dry-run vs confirm execution. Lacks explicit when-not scenarios beyond creation.

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