Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createGotify

Creates a Gotify notification channel in Dokploy, configuring server URL, app token, priority, and event alerts for deployments, backups, cleanup, restarts, and server thresholds.

Instructions

POST /notification.createGotify

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>",
      "appToken": "<appToken>",
      "priority": "<priority>",
      "decoration": "<decoration>"
    },
    "name": "notification-createGotify"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appTokenYes
priorityYes
appDeployYes
serverUrlYes
decorationYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
serverThresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

The only annotation is openWorldHint=true, so the description carries nearly the full burden of behavioral disclosure and delivers none of it. It does not say that this performs an external write, what side effects result, whether the Gotify endpoint is contacted at creation time, or what happens on failure. Only the verb 'create' in the route supplies any behavioral signal.

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 text is technically short, but it is under-specified rather than concise: a bare route string with no front-loaded statement of purpose. Brevity here provides no value because nothing substantive is being communicated.

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?

For a 13-parameter mutation tool with no output schema and only minimal annotations, the description is completely inadequate. It conveys nothing about the required credentials, the event-subscription booleans, validation constraints such as minimum priority of 1, or the difference from sibling create/update/test tools.

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 parameters, all required, with 0% schema description coverage, and the description explains none of them. Fields such as serverUrl, appToken, priority, decoration, and the eight boolean event toggles (appBuildError, databaseBackup, dokployRestart, serverThreshold, etc.) are entirely undocumented, so an agent must guess their meaning and acceptable values.

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 only the HTTP route 'POST /notification.createGotify', which restates the tool name rather than explaining what the tool does. An agent can infer that a Gotify notification channel is being created, but nothing states what a Gotify notification is, what it gets attached to, or how it differs from notification-createCustom or notification-createDiscord.

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

Usage Guidelines1/5

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

There is no guidance at all about when to use this tool, no prerequisites, and no mention of alternatives. With siblings like notification-updateGotify and notification-testGotifyConnection present, the agent is left to guess that this is the creation step rather than an update or a connectivity test.

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