Skip to main content
Glama

pmg_action_notification_create

Create a notification action rule for PMG to send email alerts. Use dry-run to plan changes before confirming.

Instructions

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

List existing action objects with pmg_action_objects_list; attach this one to a rule with pmg_ruledb_rule_action_attach. Needs PROXIMO_PMG_* config. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesNotification recipient email address.
infoNoOptional free-text description.
nameYesName for the new notification action object.
attachNoIf True, attach the original message to the notification.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
subjectYesNotification email subject line.
body_textYesNotification email body text; maps to API param 'body'.
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 burden. It discloses mutation behavior, dry-run default, execution trigger (confirm=True), and the return format for execution. It also mentions the config requirement. It does not cover rate limits, idempotency, or side effects on existing objects, but the provided information is good.

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, well-structured, and front-loaded with key information. Every sentence adds value: mutation type, dry-run behavior, related tools, config requirement, and execution details. No unnecessary words.

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 8 parameters, no annotations, and presence of an output schema, the description covers creation workflow, config, dry-run, and execution response. It lacks information on error handling, validation, or limits, but is fairly complete for a tool with an output schema.

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%, so baseline is 3. The description adds context for confirm (dry-run by default) and attach ('attach the original message'), and mentions the config requirement relating to proximo_target. It does not significantly extend meaning beyond schema for name, info, subject, body_text, to.

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 action: 'create a notification action object in the PMG RuleDB'. It specifies verb and resource, and distinguishes from sibling tools like pmg_action_objects_list and pmg_ruledb_rule_action_attach by mentioning them as related 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?

The description provides clear usage context: dry-run by default, confirm=True to execute, and a workflow (list, create, attach). It mentions the config requirement (PROXIMO_PMG_*). However, it does not explicitly state when not to use this tool or provide alternatives for different notification actions (e.g., update).

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