Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createMattermost

Create a Mattermost notification integration by supplying a webhook URL and choosing Dokploy events, such as deploys, backups, errors, restarts, cleanup, or server thresholds, to alert on.

Instructions

POST /notification.createMattermost

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

Input Schema

NameRequiredDescriptionDefault
nameYes
channelNo
usernameNo
appDeployYes
webhookUrlYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
serverThresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.1/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, which suggests external side effects but gives no detail. The description adds nothing about mutating state, whether a duplicate connection is rejected, what permissions or webhook validity are required, or what happens on failure.

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 conveys no information and is not front-loaded with any actionable 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 a 12-parameter creation tool with no output schema and near-zero annotation coverage, the definition supplies none of the context needed to call it correctly. The agent would have to guess the semantics of every required field.

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 12 parameters (10 required) at 0% schema description coverage, and the description provides no meaning for any of them. The agent cannot tell from either source what the boolean flags (appDeploy, dokployBackup, serverThreshold, etc.) enable, nor how webhookUrl, channel, and username relate.

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

Purpose1/5

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

The description is only "POST /notification.createMattermost", which restates the tool name as an HTTP route and says nothing about what the tool actually does. It never states that a Mattermost notification channel is being created, nor which fields configure it.

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 when-to-use guidance, no mention of prerequisites such as an incoming webhook, and no distinction from siblings like notification-updateMattermost or notification-testMattermostConnection. The agent must infer everything from the name.

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