Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateEmail

Idempotent

Updates an existing email notification configuration by ID so you can change SMTP settings, credentials, recipients, and alert triggers.

Instructions

POST /notification.updateEmail

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": {
      "notificationId": "<notificationId>",
      "emailId": "<emailId>"
    },
    "name": "notification-updateEmail"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailIdYes
passwordNo
smtpPortNo
usernameNo
appDeployNo
smtpServerNo
fromAddressNo
toAddressesNo
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
serverThresholdNo

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 declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond the bare route. It never states that this mutates an existing email notification config, what fields get overwritten, whether credentials like password are re-required, or that SMTP changes may break delivery. For an 18-parameter mutation tool this is a severe disclosure gap.

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 brevity here comes from under-specification rather than efficiency. A route string is not a meaningful front-loaded summary of an 18-parameter update operation.

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?

There is no output schema and no parameter documentation, so the description must carry the full burden of explaining behavior. It delivers none of it, leaving the agent unable to call this correctly without guessing at field semantics and update scope.

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 18 parameters, including credentials (password, username, smtpServer) and boolean event toggles (appDeploy, databaseBackup, serverThreshold), so the schema carries no semantics at all. The description supplies no parameter meaning whatsoever, leaving every field undocumented.

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 'POST /notification.updateEmail', which restates the tool name in HTTP-method form rather than explaining what the operation actually does. It implies updating an email notification configuration but says nothing about the scope of that update and does not distinguish it from siblings such as notification-createEmail or notification-updateCustom.

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 prerequisites, and no mention of alternatives, even though siblings like notification-createEmail and notification-testEmailConnection sit adjacent in the catalog. An agent gets zero help deciding between updating existing email settings and creating new ones.

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