Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createEmail

Creates an email notification configuration in Dokploy, defining SMTP settings, recipients, and alert triggers for deployment, backup, and server events.

Instructions

POST /notification.createEmail

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>",
      "smtpServer": "<smtpServer>",
      "smtpPort": "<smtpPort>",
      "username": "<username>",
      "password": "<password>",
      "fromAddress": "<fromAddress>",
      "toAddresses": "<toAddresses>"
    },
    "name": "notification-createEmail"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
passwordYes
smtpPortYes
usernameYes
appDeployYes
smtpServerYes
fromAddressYes
toAddressesYes
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?

The only annotation is openWorldHint=true; the description contributes nothing beyond the HTTP verb. For a mutating tool with 15 required fields, it says nothing about whether the record must be unique, what happens on duplicate names, whether credentials are validated against the SMTP server, 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 short here means under-specified rather than concise: the single route token conveys no information an agent could not already derive from the tool name. Nothing is front-loaded because there is no content to front-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 15 required parameters, no output schema, and only an openWorldHint annotation, this definition is completely inadequate. An agent cannot construct a valid call — particularly the SMTP credential set and the event-flag booleans — without outside knowledge of the underlying API.

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 15 required parameters, so the description carries the full explanatory burden and delivers none of it. Fields such as serverThreshold, dokployRestart, appBuildError, and toAddresses have no meaning supplied anywhere — the agent must guess that the booleans are event-subscription toggles and that toAddresses is the recipient list.

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.createEmail", which essentially restates the tool name rather than stating in prose what the tool does. An agent can infer it creates an email notification channel, but the definition adds no verb/resource framing beyond the name itself and does not distinguish it from sibling creators like notification-createSlack or notification-updateEmail.

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 on when to use this tool, when not to, prerequisites, or how it relates to notification-updateEmail, notification-testEmailConnection, or the other create* channel tools. The agent must infer everything from the name and sibling list.

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