Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createPushover

Create a Pushover notification channel for Dokploy using a user key and API token, and configure priority, retry/expire rules, and event triggers for deployment and backup alerts.

Instructions

POST /notification.createPushover

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "userKey": "<userKey>",
      "apiToken": "<apiToken>"
    },
    "name": "notification-createPushover"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
retryNo
expireNo
userKeyYes
apiTokenYes
priorityNo
appDeployNo
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
serverThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The only annotation is openWorldHint=true and a title; there is no readOnlyHint or destructiveHint, so the description carries the full burden for a 14-parameter mutation. It discloses nothing about auth requirements (userKey/apiToken), side effects, whether duplicate channels are rejected, or how the retry/expire/priority limits behave. This is a bare endpoint restatement with zero behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity reflects under-specification rather than economy; a single endpoint path is not a front-loaded explanation of purpose. Nothing in the string earns an agent's trust about what happens on invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter creation tool with no output schema and no meaningful annotations, the definition is far too thin. It says nothing about required credentials, whether the created channel is immediately active, or the relationship to the boolean event toggles, so an agent cannot call it reliably without reading the raw schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 14 parameters, so the description must compensate and does not: it adds no meaning for name, userKey, apiToken, retry, expire, priority, or the eight event-toggle booleans (appDeploy, volumeBackup, dockerCleanup, serverThreshold, etc.). Given the complete coverage gap, the description fails to supply even minimal semantics such as what a toggle enables or the units of retry/expire.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is nothing but the HTTP verb and endpoint path, "POST /notification.createPushover", which restates the tool name rather than explaining what it does. An agent can infer that a Pushover notification channel is created, but only from the name, not from any stated purpose or scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternatives in the sibling list such as notification-testPushoverConnection or notification-updatePushover. The agent must infer the create-versus-test-versus-update distinction entirely from sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools