Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createNtfy

Creates and configures an Ntfy notification channel in Dokploy to alert on deployments, backups, build errors, cleanup, restarts, and server thresholds.

Instructions

POST /notification.createNtfy

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": {
      "appBuildError": "<appBuildError>",
      "databaseBackup": "<databaseBackup>",
      "dokployBackup": "<dokployBackup>",
      "volumeBackup": "<volumeBackup>",
      "dokployRestart": "<dokployRestart>",
      "name": "<name>",
      "appDeploy": "<appDeploy>",
      "dockerCleanup": "<dockerCleanup>",
      "serverThreshold": "<serverThreshold>",
      "serverUrl": "<serverUrl>",
      "topic": "<topic>",
      "accessToken": "<accessToken>",
      "priority": "<priority>"
    },
    "name": "notification-createNtfy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
topicYes
priorityYes
appDeployYes
serverUrlYes
accessTokenYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
serverThresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true and a title, so the description carries the full behavioral burden and provides none. It does not state that this is a mutating write operation, whether it requires credentials or admin rights, whether the channel is tested/activated immediately, or how failures are surfaced.

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?

The single line is short but conveys no information; this is under-specification rather than conciseness. Nothing is front-loaded because there is nothing to load.

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

Completeness1/5

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

Given 13 required parameters, no output schema, and near-zero annotation coverage, the description is wholly inadequate for correct invocation. An agent would have to guess at every field's meaning and accepted values.

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?

There are 13 required parameters at 0% schema description coverage, and the description explains none of them. The boolean flags (appDeploy, serverThreshold, dockerCleanup, etc.) are completely ambiguous without definitions, and the ntfy-specific fields (topic, serverUrl, accessToken, priority) get no explanation of format or semantics.

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 just 'POST /notification.createNtfy', which restates the tool name and HTTP route without explaining what a ntfy notification channel is or what creating one accomplishes. An agent learns nothing beyond the fact that it is a create operation, and the sibling set (createDiscord, createSlack, updateNtfy, testNtfyConnection) is not differentiated.

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 distinction from notification-updateNtfy or notification-testNtfyConnection, and no prerequisites (e.g., that a serverUrl and accessToken must be valid before creating). Usage is only implied by the verb 'create'.

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