Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createDiscord

Creates a Discord notification channel for Dokploy by configuring a webhook URL and selecting deployment, backup, cleanup, restart, build-error, and server-threshold events to alert on.

Instructions

POST /notification.createDiscord

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>",
      "webhookUrl": "<webhookUrl>",
      "decoration": "<decoration>"
    },
    "name": "notification-createDiscord"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appDeployYes
decorationYes
webhookUrlYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
serverThresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/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. The description adds nothing about what the call mutates, whether it is idempotent, what permissions or a valid webhook URL are required, or what happens on duplicate names — despite this being a write operation against an external service.

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 comes from under-specification rather than efficiency — a single route string carries no actionable information and is not front-loaded with purpose.

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 an 11-required-parameter mutation tool with zero schema coverage, no output schema, and minimal annotations, the description should explain the parameters and side effects. It provides none of that, leaving the definition unusable without external knowledge.

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 11 required parameters. The description provides no meaning for name, webhookUrl, or the eight undocumented boolean event toggles (appDeploy, serverThreshold, dockerCleanup, etc.), so an agent must guess every field's 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?

"POST /notification.createDiscord" only restates the tool name as an HTTP route. It implies creating a Discord notification but never states what is created, what the boolean flags mean, or how it differs from notification-updateDiscord or the other create* siblings.

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?

No when-to-use guidance at all: nothing says whether this registers a new Discord webhook notification channel, whether a webhook must exist first, or when to prefer notification-updateDiscord or notification-testDiscordConnection.

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