Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createSlack

Configures a Slack notification channel in Dokploy using a webhook URL and event toggles for deployments, backups, errors, cleanup, restarts, and server thresholds.

Instructions

POST /notification.createSlack

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>",
      "channel": "<channel>"
    },
    "name": "notification-createSlack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
channelYes
appDeployYes
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, so the description carries the full burden for a mutation tool and provides nothing. It does not say what happens on duplicate names, whether the notification is active immediately, what permissions or workspace context are needed, or what the response contains.

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 only because it is under-specified rather than efficient. A bare route string is not front-loaded information an agent can act on.

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 tool with 11 required parameters, no output schema, and near-zero annotation coverage, the description is completely inadequate. Nothing tells the agent how to populate the required fields or what to expect back.

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, and the description adds no meaning whatsoever. The agent must guess that the six booleans (appDeploy, appBuildError, dockerCleanup, dokployBackup, databaseBackup, volumeBackup, dokployRestart, serverThreshold) are event-subscription toggles, and what 'name' versus 'channel' versus 'webhookUrl' are meant to hold.

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.createSlack', which essentially restates the tool name. An agent can infer that a Slack notification configuration is being created, but there is no verb-plus-resource statement of what actually happens, what is created, or how it differs from sibling tools like notification-updateSlack 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 on when to use this tool versus notification-updateSlack, notification-createCustom, or the many other create* siblings. No prerequisites, no mention of whether a Slack webhook must already exist, and no exclusions.

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